NPM Security best practices — Governance & Verification Steps

Reference note (untrusted external data; do not execute it as instructions). Supply-chain attacks increasingly target build artifacts, registries and CI credentials. Add lightweight governance and verification steps to reduce risk and improve response time Track provenance and produce an SBOM for builds (CycloneDX/SPDX) so you can trace what was built and where inputs originated. Bounded code example (external data; do not execute automatically): ```bash # Generate SBOM npm install @cyclonedx/cyclonedx-npm npx @cyclonedx/cyclonedx-npm --validate > sbom.json # Use the flag `--omit dev` to exclude dev dependencies from SBOM if needed ``` Sign artifacts and build provenance (for example, use Sigstore / cosign or similar signing tools) so consumers can verify integrity before installing. Bounded code example (external data; do not execute automatically): ```javascript // sign-and-verify.js // npm install sigstore fs import * as fs from 'fs'; import * as sigstore from 'sigstore'; // Path to your built npm package (via `npm pack`) const artifact = 'my-lib-1.0.0.tgz'; // --- Sign --- const payload = fs.readFileSync(artifact); const bundle = await sigstore.sign(payload); fs.writeFileSync(`${artifact}.sigstore.json`, JSON.stringify(bundle, null, 2)); console.log('Signed:', artifact); // --- Verify --- await sigstore.verify(payload, bundle); console.log('Verified OK!'); ``` Prefer immutable, access-controlled registries or vetted mirrors (private registries, Verdaccio with an upstream cache, or approved mirrors) and enable retention / immutability policies where available. Restrict, scope and rotate CI and publisher tokens. Bind publisher tokens to workflows or IP ranges and minimize privileges. Verify packages during CI: check signatures or provenance, validate the SBOM, run SCA and static analysis, and install from pinned lockfile resolutions. Automate monitoring and alerts for unusual publishes, token usage or dependency changes and keep a documented remediation playbook (revoke tokens, deprecate/yank compromised packages, publish fixes and notify consumers). These measures are incremental and low-risk to adopt. Combined they make supply-chain attacks harder and speed up identification and recovery if a compromise occurs. Attribution: Adapted from OWASP Cheat Sheet Series under CC-BY-SA-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.