[codex] Add GitHub DevSecOps workflows#40
Closed
ganesh47 wants to merge 2 commits into
Closed
Conversation
Owner
Author
|
Superseded by #39, which has already been merged into main. |
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.
What changed
This PR adds a GitHub-based DevSecOps baseline for
cstack.docs/devsecops.mdpackage.jsonpackage-manager metadata with the repo's actual npm-based workflow contractWhy
The repo already had CI and release automation, but it did not have durable dependency automation, PR-level security gates, scheduled security evidence, or release supply-chain hardening. This closes that gap without changing the existing core build/test/release intent.
Impact
validate,dependency-review,CodeQL, andGitleaksValidation
npx --yes actionlintnpm run buildnpx vitest run test/deliver.test.ts --reporter=dot