Conversation
![korbit-ai[bot]](https://avatars.githubusercontent.com/in/322216?s=60&v=4){kind=small}
Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
spoorcc
force-pushed
the
spoorcc/issue784
branch
from
8153cad to
f8fdb07
Compare
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
2 participants
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.
Fixes #784
Description by Korbit AI
What change is being made?
Enforce stronger security hygiene across CI/CD and developer tooling by pinning actions, adding runner hardening and audit steps, introducing a Dependency Review workflow, updating DevContainer and docs, and minor test/util updates (including gitleaks pre-commit hook and svn-error handling in tests).
Why are these changes being made?
Improve the OpenSSF score and overall security posture by auditing outbound calls, restricting permissions, and using deterministic actions/images; centralize security guidance and tooling (dependency review, code scanning, secrets hygiene) to reduce risk.