-
Notifications
You must be signed in to change notification settings - Fork 155
Maintenance: Improve security posture by addressing OpenSSF results #1799
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
Comments
The "on new PR" workflow is failing due to it attempting to obtain more elevated permissions than the caller workflow - see an example here. Would appreciate if you could take a look. cc @am29d. |
The "On PR merge" workflow is also failing due to permission issues: https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/7292228413/job/19872848955 |
With the release workflow merged we have completed most of the work needed for the OpenSSF scorecard. After discussing internally, these are the pending items for the next iteration, after which we can close the topic:
|
With #2072 being merged we can now consider concluded the work needed to improve the security posture of the project. |
This issue is now closed. Please be mindful that future comments are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so. |
Summary
We recently added OpenSSF Scorecard to the repository, on the initial scan, it found a few actionable items.
Why is this needed?
OpenSSF Scorecard scanner found minor issues with the project that we should improve on.
Which area does this relate to?
Governance
Solution
No response
Acknowledgment
Future readers
Please react with 👍 and your use case to help us understand customer demand.
The text was updated successfully, but these errors were encountered: