Estimated reading time : 5 min · Published
Connect each dependency to its purpose
Inventory direct components and dependencies brought in by tools. Record the installed version, registry or supplier, supported feature and update owner. Include CMS plugins rather than only developer-managed packages.
Ask a simplification question: if the feature disappeared, which useful journey would be lost? An installed but forgotten component adds work without establishing its value. Consider removal only after checking dependent content, data and components.
Assess an alert against the actual project
Compare the affected package and version with the inventory. Examine exposure conditions, the announced fix and related dependencies. An alert does not describe the entire architecture, and absence of alerts is not a security guarantee.
Document a reason for priority: exposed functionality, affected data, known exploitation or required change. Where the situation is uncertain, involve a qualified reviewer rather than replacing uncertainty with a score presented as certainty.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Situation or setting | What it means | Useful check |
|---|---|---|
| Affected version installed | Compare the resolved version with the security advisory. | Do not conclude from the package name or a theoretical version range alone. |
| Affected feature used or exposed | Identify the real project path and advisory conditions. | Apparent non-use needs verification; it does not justify ignoring an update. |
| Third-party resource with integrity metadata | Compare the file, version and expected hash. | A hash checks content correspondence, not the absence of vulnerabilities. |
Prepare a reproducible update
Keep files describing resolved versions and build steps. Use a representative test environment, synthetic data and a suitable backup. Compare affected journeys such as search, forms, checkout or administration according to the component.
npm provenance connects a published package with source and build information; it does not certify that the package is safe. Review available evidence without treating provenance as an automatic installation recommendation.
Fictional example: component DEMO-PKG is declared with range ^2.4.0, but the lockfile and deployed artifact reference indicate 2.4.1. The advisory invented for this exercise covers versions 2.4.0 through 2.4.2 and proposes 2.4.3. The declaration already permits that fix among compatible stable releases; it does not prove the fix has been resolved, built or deployed.
In npm, npm ci uses the existing lockfile rather than updating it to select a newer fix. Compare the declaration, resolved version, build artifact and version actually served. After a prepared update, the table requires reconciliation with 2.4.3 and tests of the affected journey. This version and advisory are fictional; matching them does not guarantee the absence of other defects.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Checked reference | Exercise value | What it establishes |
|---|---|---|
| Manifest declaration | ^2.4.0 | Permitted stable-version range, not deployed version |
| Lockfile before the fix | 2.4.1 | Resolved version still covered by the fictional advisory |
| Deployed artifact before the fix | Reference 2.4.1 | Fix 2.4.3 is not yet evidenced in production |
| After a controlled update | Lockfile, build and served artifact: 2.4.3 | Expected reconciliation, then functional tests and release decision |
- npm : npm ci
npm, consulted 22 October 2026: npm ci behaviour. DEMO-PKG, the versions and advisory form a fictional scenario.
- npm/node-semver : Caret Ranges
npm/node-semver, consulted 22 October 2026: version ranges and prerelease rules.
Record the result and recovery plan
Record versions before and after, passed tests, unchecked areas and the release decision. Recovery must include data when an update changes its structure; replacing files alone may be insufficient.
Choose the next review according to the component’s role and team capacity. The deliverable is a list of useful components with origin, owner, tests and recovery rather than a schedule of blind automated changes.
Primary documentation : npm : Generating provenance statements.
Check third-party JavaScript or CSS pinned to a fixed version.
Synthetic case: a component loads a versioned file from a CDN. Generate a hash matching that exact file and check CORS conditions. Alter the test copy: the resource should be refused. A third-party script that changes automatically needs a different strategy; an outdated hash breaks its loading.
- The expected version works; altered content is blocked and hash updates are planned.
- MDN Subresource Integrity
Mechanism for comparing a fetched resource with an expected hash before the browser uses it.
Decide in a concrete situation
Fictional example: a major update fixes a problem but breaks an essential extension. Identify uses and version constraints, prepare an isolated trial and an alternative; installing the latest release does not finish the task.
Record direct or indirect dependency, version, use, owner and test result. Preserve reproducible configuration without secrets; relate a security advisory to the component and context actually deployed.
- Protect and test a website staging environment
Separate access control from indexing, prevent real messages and transactions, use synthetic data and verify the production transition.
Reference documents
- MDN Subresource Integrity · Source consulted
- npm : Generating provenance statements
Content updated on
