DATA-13529: add hardened .npmrc - #33
Merged
Merged
Conversation
bs-amitmahajan29
approved these changes
Jul 29, 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.
Closes the weekly supply-chain
.npmrcaudit finding for this repo (DATA-13529 / SC-12282). Adds the required hardening directives, matching the existing.npmrcinbrowserstack/dwh_node.Why this is non-breaking
ignore-scripts=truepackage-lock.jsonhas zero packages with install scripts;package.jsonhas no pre/post scripts — no-opengine-strict=truepackage.jsonhas noenginesfield — no-opsave-exact=truenpm install <pkg>; existing^ranges are untouchedaudit-level=highnpm auditexit code; the only CI workflow is Semgrep, which does not runnpm auditlegacy-peer-deps=falsepeerDependenciesin the dependency treestrict-ssl=truemin-release-age=7npm cireplays the lockfile, and every locked version here is years old — no effect. Added in npm 11.10; older npm just warns the key is unknown. Required by Semgrep rulenpm-missing-minimum-release-ageaccess=restrictedis intentionally omitted — the audit requires it for private repos only, and this repo is public.Note:
.npmrcis never included in a published npm tarball, so consumers are unaffected.###JIRA
https://browserstack.atlassian.net/browse/DATA-13529