TL;DR: Software supply chain failures can shift after creation as upstream signals, dependencies, or vulnerability data change, according to Codenotary. That makes trust a moving target for build and release governance, not a one-time approval.
Editorial analysis by NHI Mgmt Group, based on content published by Codenotary: “Protecting the Software Supply Chain”.
Key questions
A: Weak governance increases risk because software supply chain decisions depend on consistent evidence, risk tolerance, and escalation.
Q: What signs show that artifact trust controls are not working?
A: Warning signs include stale approvals, no re-evaluation when vulnerabilities change, weak visibility into dependency lineage, and build or release paths that cannot explain why an artifact is trusted.
Q: How should teams govern supply chain risk in CI/CD environments?
A: Use separate identities for build, sign, and deploy, and make credential scope as narrow as the task allows.
Practitioner guidance
- Implement continuous artifact re-scoring Re-evaluate trust for build outputs, containers, and packages whenever upstream vulnerability or lineage signals change, rather than only at release time.
- Inventory pipeline identities and publishing paths Map service accounts, tokens, signing identities, and release permissions that can create or promote artifacts across CI/CD.
- Blend internal lineage with external risk feeds Correlate attestations, build metadata, open source risk scores, and vulnerability feeds so affected artifacts can be flagged quickly.
Bottom line: The article frames software supply chain failures as a lifecycle governance problem, not just a provenance problem.
Glossary terms: Artifact Trust, Software Supply Chain Security, Pipeline identity, Claim Trust Drift
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Continuous trust scoring is becoming the missing control plane for software supply chain governance. Provenance alone tells teams where an artifact came from, but not whether its risk changed after creation. The article is right to frame trust as something that must be re-evaluated across the lifecycle, especially when dependencies and build systems move faster than manual review. Practitioners should treat trust scoring as an operational governance layer, not a reporting metric.
A few things that frame the scale:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should teams do when a previously trusted artifact becomes high risk?
A: They should be able to isolate the artifact, stop further promotion, identify all affected downstream systems, and re-score related builds or packages immediately. The governance objective is containment and decision speed. If the organisation cannot revoke trust quickly, the original compromise will continue to spread through legitimate software processes.
👉 Read our full editorial: Continuous artifact trust scoring raises the bar for supply chain risk