add openssf scorecard scanning/badge and clomonitor exemption #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please specify the area for this PR
What does does this PR do / why we need it:
This addresses the adding of certain open source best practices that we are adding to all of our repositories. These practices include the scorecard code scanning tool that checks for security vulnerabilities in our repositories as well as providing a score for the repository in the form of a badge. Additionally it adds the badge for the best practices checklist.
Note that on the CLOMonitor there will be missing checks for
Artifact HubandRecent Release. I don't see a point in markingArtifact Hubas exempt if there is items that can be added for this repository, and there are issues open to add them (helm charts). ForRecent Releasethere was a release in 2022 but the check is only for <= 1 year. This will be remedied whenever a new release comes along and should not be exempted also.Which issue(s) this PR fixes:
fixes devfile/api#1387
PR acceptance criteria:
Documentation (WIP)
How to test changes / Special notes to the reviewer: