Repository navigation
ci: add an opt-in npm dependency report - #140
Open
PresentJay wants to merge 1 commit into
Open
PresentJay wants to merge 1 commit into
PresentJay wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Author
|
I contribute to zero-shelter and proposed this as a manual npm report alongside the extension’s build and type checks. The zero-finding capture in the description is a saved result, not a current security assessment. Would this report format add anything useful to your existing dependency review? |
Member
|
I see the use case, but I don't think we really need it. |
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.
This offers a manual view of the extension’s npm lockfile alongside its existing build and type checks. I’m developing zero-shelter and trying it in existing projects to learn where a dependency report adds useful context.
This PR adds one separate Dependency triage report workflow with only a
workflow_dispatchtrigger. It collects npm audit JSON using--package-lock-only --ignore-scripts, renders it withzero-shelter@0.0.10, and keeps an HTML artifact for seven days. Permissions arecontents: read; the job installs no project packages and does not accept a baseline. Finding exit1and judgement-error exit2stay failures.The local capture from 2026-11-02 UTC, at base
09ff4c3011d0, had 0 raw / 0 merged / 0 outstanding / 0 accepted findings. npm audit and both JSON/HTML commands returned0; a synthetic failed-scanner input returned2. YAML, shell syntax and whitespace checks passed, and the manifest and lockfile hashes matched. This is the saved npm-only result, not a new scan. I did not run the extension test/build checks or the new hosted manual workflow.npm audit queries the configured registry;
npxdownloads and runs third-party code in CI even with read-only repository permissions. Reachability and exploitability remain unverified. Implementation and this description were prepared with AI assistance.Would a report like this be useful alongside the extension checks? I’m happy to withdraw it if your existing dependency review already covers what you need.