Manifest-based discovery reads declared packages from files such as pom.xml or setup.py, while full dependency-tree resolution follows the package manager’s own logic to include direct and transitive dependencies. Full resolution is more complete because it captures what the application actually pulls in at scan time. That matters when security teams need a trustworthy inventory for risk analysis.
How manifest-based discovery differs from full dependency-tree resolution
Manifest-based discovery starts from the files the developer declared, so it is fast and predictable, but it can miss what the package manager actually adds at install time. Full dependency-tree resolution follows resolver logic end to end, which makes it better for understanding the real software bill of materials, transitive risk, and hidden exposure introduced through nested packages.
That distinction matters because scanners, SCA tools, and review workflows can produce different inventories depending on whether they stop at the manifest or mirror the resolver’s full graph. The practical question is not just “what did the author list?” but “what code and packages will actually be present when the application builds or runs?”
For open-source ecosystems, the gap is especially important when dependency metadata is incomplete, ambiguous, or altered by lockfiles, version ranges, extras, optional dependencies, or platform-specific resolution. A manifest may show intent, while the resolved tree shows operational reality, and those two views are not always the same.
Why full resolution gives a more trustworthy risk picture
Security teams usually want the answer that best matches runtime or build-time exposure, not the narrowest declaration set. Full resolution is more complete because it includes transitive dependencies, which are often where vulnerable libraries, stale subcomponents, and policy violations enter the environment. For that reason, OpenSSF is relevant whenever dependency hygiene is being treated as a supply-chain control problem rather than a purely developer-facing checklist.
Manifest-only discovery still has value. It is useful for quick triage, repository hygiene checks, and situations where you want to know what the team explicitly intended to use. But if the goal is risk analysis, incident response scoping, or compliance evidence, the higher-fidelity dependency tree is usually the better source of truth.
The main trade-off is operational complexity. Full resolution can require access to the correct package manager, lockfiles, build context, private registries, and platform rules, so it is more expensive to collect and easier to mis-scan if the environment is not reproduced faithfully.
What changes for inventory, governance, and supply-chain controls
The difference affects how you design inventory controls. If you only catalogue manifests, you may undercount the actual attack surface and miss a vulnerable transitive package that never appears in the top-level file. If you only trust resolved trees, you may lose the developer’s declared intent and make change review harder, especially when dependency graphs are large or frequently regenerated.
That is why teams often use both views together: manifest-based discovery for intent, and dependency-tree resolution for exposure. In practice, the second view is the one that helps answer whether a vulnerable component is truly reachable in the software that ships, and whether a new package entered through a nested path rather than a direct request.
This distinction also affects policy enforcement. A package allowlist, license review, or vulnerability gate that only inspects manifests can be bypassed by transitive additions. A more complete scan should be able to explain not just that a package exists, but why it exists and which parent introduced it.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8, SLSA and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-16 — Application Software Security | Dependency discovery supports secure software inventory and vulnerability awareness. |
| Recommendation — Track third-party dependencies and update them through secure software maintenance. | ||
| SLSA | Supply chain integrity | Resolved dependency trees support provenance and integrity checks for shipped software. |
| Recommendation — Require build provenance evidence that matches the resolved artifact tree. | ||
| NIST CSF 2.0 | ID.AM-01 — Physical devices and systems within the organization are inventoried | Dependency inventory is an asset-identification problem for software components. |
| Recommendation — Inventory software components with the same rigor as other assets. | ||
Practitioner Guidance
What to verify: Confirm that your scanning process reproduces the same resolver behaviour used by the build system, including lockfiles, extras, optional dependencies, and platform markers. If your scan environment cannot do that, treat the result as directional rather than authoritative.
Decision rule: Use manifest discovery for fast repo-level review, but use full dependency-tree resolution whenever the output will drive remediation priority, risk acceptance, or executive reporting. If the two results disagree, investigate the resolver path before trusting either inventory.
Practitioner takeaway: The most defensible dependency view is the one that matches how the software is actually assembled, not the one that is easiest to collect.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org