MAINT: Harden frontend npm config (npm audit + min-release-age) - #2103
Merged
romanlutz merged 2 commits intoJun 30, 2026
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jbolor21
approved these changes
Jun 30, 2026
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.
Description
Config-only maintenance for the frontend's npm supply-chain posture, plus a small housekeeping ignore.
frontend/.npmrc— three settings appended; the existing registry pin on line 1 (CSSC CFS0001) is left untouched:min-release-age=7: refuse package versions younger than 7 days, to dodge freshly-published malicious releases (supply-chain mitigation against attackers who publish a compromised version hoping it is pulled in before detection/yanking).audit=true: runnpm auditautomatically on install so known vulnerabilities surface immediately.audit-level=high: only high/critical advisories cause a non-zero (CI-failing) exit, keeping the signal actionable..gitignore— ignore the.impeccable/directory, a local per-session cache created by tooling. It is not part of PyRIT and should never be committed.Tests and Documentation
No code or tests changed — these are configuration-only changes. JupyText is not applicable (no docs or notebooks were touched).