Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O org.eclipse.dash.handbook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 156
    • Issues 156
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Technology
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #150
Closed
Open
Issue created Feb 23, 2021 by Wayne Beaton@wbeatonMaintainer

Add a requirement/recommendation to provide a SECURITY file with project documentation

Consider requiring/recommending that projects include a SECURITY file in their repositories.

The file should include a pointer to the Eclipse Foundation Vulnerability Reporting Policy along with implementation details that are specific to the project.

What implementation details should be included in the file?

  • By what mechanism should vulnerabilities be reported
  • How vulnerabilities are tracked by the project team
  • By what criteria the project team will decide whether or not a CVE will be requested from the Eclipse Foundation

What else?

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent