ci: standardize security posture (gitleaks + dependency-review + scorecard, explicit permissions)#576
Merged
Merged
Conversation
…rmissions
Bring the Security workflow to the standard netresearch posture: secret
scanning (gitleaks), dependency review on PRs, and OpenSSF Scorecard,
alongside the existing Node.js audit. Every reusable caller job declares
its exact permission union (top-level `permissions: {}`), so the token is
explicit and never relies on the repository default.
Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
Contributor
Dependency ReviewThe following issues were found:
License Issues.github/workflows/security.yml
OpenSSF Scorecard
Scanned Files
|
|
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.


Standardizes the Security workflow to the netresearch posture used by the other repo classes:
Every reusable caller job declares its exact permission union under a top-level
permissions: {}, so the token passed to each reusable is explicit and never relies ondefault_workflow_permissions— making the planned org-wide default→read flip safe. Customcodeql.ymlis unchanged.