TL;DR: Open-source supply chain risk now includes abandoned projects, end-of-life packages, delayed fixes and AI-hallucinated dependencies, Anchore says. SBOMs matter more when they carry provenance, maintenance and lifecycle signals that help teams decide what to trust.
Editorial analysis by NHI Mgmt Group, based on content published by Anchore: “Why Vulnerabilities Aren’t Enough: Threat Hunting Your Open Source Code”.
Key questions
Q: What breaks when dependency governance is still treated as a scanner problem?
A: Teams end up with accurate inventories but no practical closure.
Q: How do AI-generated package names increase software supply chain risk?
A: They create a verification failure.
Q: How do organisations decide when to trust an audited open-source dependency?
A: They should trust the dependency only after the audit, remediation, and release cycle are all visible.
Practitioner guidance
- Build dependency trust scoring into approval workflows Combine CVE results with package age, release cadence, maintainer activity and end-of-life signals before a dependency is approved for use.
- Enrich SBOMs with source-of-truth metadata Map each listed component back to its canonical repository or package source, then attach lifecycle and maintenance indicators to the record.
- Block unverified AI-suggested imports Require review when code generation proposes dependency names, and reject packages that cannot be tied to an expected canonical source.
Bottom line: Open-source risk is no longer limited to disclosed vulnerabilities, because abandoned projects and fake packages can be just as dangerous.
Glossary terms: Software Bill of Materials, Software Supply Chain, Dependency Trust Scoring, Provenance
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Dependency trust is now the control problem, not just vulnerability discovery. The article shows that a package can be risky even when no CVE exists, because abandonment, end-of-life status and slow patching all undermine trust. That means security teams need to evaluate whether a dependency deserves inclusion at all, not only whether it is already known to be vulnerable. The practical conclusion is that software assurance has to move upstream into provenance, lifecycle and maintainership checks.
A few things that frame the scale:
- Software supply chain attacks were projected to cost organisations $60 billion in 2025.
A question worth separating out:
Q: Should organisations prioritise SBOM enrichment over more vulnerability scans?
A: Yes, when the problem is trust in third-party components rather than only known exploits. Vulnerability scans tell you what is already disclosed, while SBOM enrichment tells you whether the dependency should be trusted in the first place. For modern supply chains, lifecycle, provenance and maintainer signals often change the decision more than another CVE result does.
👉 Read our full editorial: Open-source dependency risk now extends beyond CVEs