chore(ci): introduces OSSF Scorecard #2512
Merged
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.
Issue number: #2203
Summary
Introduces Open-source Security Foundation Scorecard checks.
It also gives us a score that we can publish as a GitHub Badge later. At first, it'll complain about our lack of provenance (SLSA) and binary signing - these are depending GitHub investigation to ensure published release notes don't disappear with git tags being created from our release workflow.
Changes
User experience
OSSF Scorecard should create new security alerts that could affect supply chain here: https://github.com/aws-powertools/powertools-lambda-python/security
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.