#071Technical3 min
Understand vulnerable dependencies
Read package advisories, distinguish an installed version from actual use, and plan a reviewed update.
Hackaiz team · updated 21/11/2026

01Start with the package and its installed version
A dependency is a library your application uses instead of implementing every function itself. Some are selected directly; others arrive through another library. A vulnerable dependency finding means a known security advisory applies to a package version found during the analysis. It does not, on its own, demonstrate that someone has attacked your application or that every use of that library exposes the vulnerable behaviour.
Hackaiz’s dependency control compares known advisories with real versions in the project’s lockfile, the file that records resolved package versions. Read the evidence for the package name, version and advisory reference before choosing an update. A version range in package.json expresses what may be installed; it is not the same as the resolved version. For example, changing a declared range without refreshing the lockfile can leave the application using the affected release.
02Separate presence, import and exploitability
Open your project from Projects, select the relevant entry in Scan history, then examine the dependency finding in the report. Identify whether the evidence comes from repository files, package metadata or another analyzed source. These are different observations. A package analysis can consult registry information and OSV, a database of security advisories; this is not equivalent to observing the code path used by your running application.
Where import evidence is available, it only establishes that a package is referenced by the first-party source examined. For example, importing lodash/merge supports saying that lodash is imported. It does not prove that the vulnerable function is called with attacker-controlled data. Conversely, no import found is not proof of safety: the available files may omit a service or a library may be loaded indirectly. If no suitable source files are available, treat usage as unknown rather than absent.
03Choose an update using the actual impact
The report uses Danger, To fix and To watch. Use that label to organize review, then read the affected component and the conditions in the advisory. Ask your developer whether the package runs on the server, in visitors’ browsers or only during development. A parsing library processing public uploads needs a different investigation from a tool used only in a restricted build environment. Neither should be dismissed solely because the application appears to work.
Prepare a targeted change: check the advisory’s fixed releases, inspect release notes for breaking changes, update the dependency and its lockfile together, and test the application paths that rely on it. If the dependency is indirect, the appropriate change may be to update its parent package rather than add a second copy manually. These are developer review steps, not a promise that Hackaiz can automatically update every package. Any Hackaiz-generated fix is a draft GitHub pull request for human review and approval; it is never merged automatically.
04Verify what changed after the update
After the reviewed update is applied, run a new analysis of the relevant connected project and inspect its evidence. Check that the analyzed version is the intended one and that the lockfile in the analyzed source really changed. A vanished advisory is useful evidence, but cannot prove the entire dependency tree is safe. A newly published advisory can also explain a finding appearing even when you did not change the code.
Analysis work and report downloads use credits. Select the relevant checks deliberately: unticked checks are not run and are not billed. Keep the before-and-after report references with the update so a reviewer can see which package was involved and what was checked. If a lookup or analysis was incomplete, preserve that limitation and repeat the missing check rather than describing the package as cleared.
Frequently asked questions
Take the next step
Was this article helpful?