Repository navigation
Harden GitHub Actions permissions and add security tooling - #268
Open
fitzyracing1 wants to merge 1 commit into
Open
fitzyracing1 wants to merge 1 commit into
fitzyracing1 wants to merge 1 commit into
Conversation
… CodeQL, SECURITY.md
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi NASA maintainers,
This PR adds some lightweight security hardening:
permissions:blocks on GitHub Actions workflows (defaulting to read-onlycontents: read)..github/dependabot.yml) for keeping GitHub Actions and dependencies current..github/workflows/codeql.yml) for code scanning.These came out of a read-only security scan of my own fork; I'm not affiliated with NASA. The changes are cherry-picked onto your current
gh-pagesand touch only config/docs, not project code.For manual review: the scan flagged an API key present in the repository. It was not changed or removed in this PR — please review/rotate it as you see fit.
Happy to adjust the scope, schedule, or contact details in SECURITY.md, or drop any part that doesn't fit your workflow. Thanks!