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

Add check for OSPS-DO-03: repo contains end-user documentation #232

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

evankanderson
Copy link
Member

This is a proposed implementation of https://baseline.openssf.org/#osps-do-03

Ideally, remediation would include creating or updating SECURITY-INSIGHTS.md, but we don't quite have those capabilities yet. I've included a sample of what we are able to do at the moment, but we'd want to be able to feed the set of discovered documentation locations into the documentation field in security-insights if not set.

@evankanderson evankanderson requested a review from a team as a code owner December 19, 2024 06:39
* A `README.md` file containing preformatted text (triple-backtick) or the headings
"usage" or "getting started"

For more information, see [OpenSSF Security Baseline](https://baseline.openssf.org/#osps-do-03).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The guidance is not meant to describe the rule type itself, but instead, to indicate what to do in case of failure. This should be moved to the description and we should tell the user what to do in case this fails.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that apply to the last sentence, or the whole current guidance?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This while guidance felt more like a description

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this read better?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants