Repository navigation
chore(deps): refresh lockfile, clear dev-dependency advisories - #14
Merged
Merged
Conversation
Regenerate package-lock.json from a clean resolve. All dependencies are devDependencies (semantic-release release tooling); the runtime itself is shell with no Node runtime deps. - Eliminates the critical handlebars JS-injection advisory - npm audit --omit=dev: 0 vulnerabilities - Remaining: braces (<=3.0.3, no upstream fix), dev-scoped, reachable only in the CI release job
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
1 participant
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.
Regenerates
package-lock.jsonfrom a clean resolve.Context: the runtime is shell;
package.jsonhasdependencies: {}. All entries are devDependencies — the semantic-release release toolchain that runs only in CI.Effect:
npm audit --omit=dev→ 0 vulnerabilities.Remaining (1):
braces <=3.0.3(high, DoS via deeply-nested glob patterns). No upstream fix (3.0.3 is latest). Dev-scoped, transitive via semantic-release/micromatch, reachable only in the CI release job — will be dismissed as 'no fix available, not in production'.Tested: no shell/runtime files changed (only the lockfile).