Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PROPOSED NEW CRITERIA - Support statement #76

Open
SecurityCRob opened this issue Nov 15, 2024 · 1 comment
Open

PROPOSED NEW CRITERIA - Support statement #76

SecurityCRob opened this issue Nov 15, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@SecurityCRob
Copy link
Contributor

We should consider adding a Lvl 1 DOCUMENTATION criteria that speaks to the need to have a published support statement/policy.

It could read something like:
"The PROJECT DOCUMENTATION MUST include a descriptive statement about how the project is supported/maintained and what is not supported. Projects are encouraged to provide "End of Support" statements when versions or features are deprecated or no longer supported."

@SecurityCRob SecurityCRob added the enhancement New feature or request label Nov 15, 2024
@SecurityCRob SecurityCRob changed the title PROPOSED NEW CRITERIA PROPOSED NEW CRITERIA - Support statement Nov 15, 2024
@eddie-knight
Copy link
Contributor

Though it needs revised, there is a Security Insights section related to this:

https://github.com/ossf/security-insights-spec/blob/main/specification/project-lifecycle.md#project-lifecycle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants