Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Practical guides

    Manage a website’s software dependencies

    A plugin or library helps build a site but creates a relationship to maintain: version, origin, support, compatibility and deployment. Useful work starts with an inventory connected to actual features.

    Go to the method

    Laptop and technical books on a desk
    AI-generated illustration

    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.

    Assess an alert before deciding
    Situation or settingWhat it meansUseful check
    Affected version installedCompare the resolved version with the security advisory.Do not conclude from the package name or a theoretical version range alone.
    Affected feature used or exposedIdentify the real project path and advisory conditions.Apparent non-use needs verification; it does not justify ignoring an update.
    Third-party resource with integrity metadataCompare 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.

    Declaration, lockfile and deployment of a fictional component
    Checked referenceExercise valueWhat it establishes
    Manifest declaration^2.4.0Permitted stable-version range, not deployed version
    Lockfile before the fix2.4.1Resolved version still covered by the fictional advisory
    Deployed artifact before the fixReference 2.4.1Fix 2.4.3 is not yet evidenced in production
    After a controlled updateLockfile, build and served artifact: 2.4.3Expected 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.

    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.

    Reference documents

    Content updated on

    Acceptance matrix to adapt to your project

    These proposed checks use synthetic cases. Decide the required behaviour with the team, record the result and assign unresolved gaps before release.

    Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.

    Test cases, expected outcomes and useful evidence
    CaseExpected outcomeEvidence to retain
    Targeted updateThe journey relying on the component retains its expected behaviour.Locked versions before and after, affected component and result of the journey depending on it.
    Disabled componentIts role and functions that stop working become explicit.Dependency list and journeys actually affected in the isolated environment.
    Clean-environment buildThe documented steps produce the expected project version.Tool versions, resolved dependency files and build log available to another maintainer.
    Return to earlier versionCode and data return to a planned compatible state.Recovery exercise, checked data and areas that could not be verified.

    Frequently asked questions

    Should every update be installed immediately?

    The answer depends on risk and the change. An urgent fix may need prompt action, whereas an incompatible release needs acceptance tests and recovery. Assess the advisory and affected journeys.

    Does provenance mean a package is safe?

    No. It establishes aspects of the relationship to source and build. It supplements version, usage, advisory and testing reviews without replacing analysis of the component and its context.