Does your private npm registry support registry signatures?
npm audit signatures works with any registry serving signing keys at /-/npm/v1/keys and signatures in package metadata. How to check yours and fix gaps.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
npm audit signatures works with any registry serving signing keys at /-/npm/v1/keys and signatures in package metadata. How to check yours and fix gaps.
Test whether a scanner reads lockfiles or only manifests: why exact versions matter, a five step PoC check, and what to do when versions are guessed.
Two person review stops a rogue commit from one account, but not a colluding pair, a build compromise or a missed diff. See what it covers and misses.
No. The Marketplace verified creator badge confirms who published an action, not that its code is safe. Here is what it means and what to check.
A quick identity check for any new dependency: confirm the repository link, owner, fork status and build source line up before you install.
Django says upgrading to the latest patch release is always the right answer. What its policy promises, and what mainstream versus extended support cover.
No. Suppressing a finding hides a vulnerability alert, not the component. The SBOM still lists the package. Share the decision through VEX instead.
Stores re-review published items and can act later, so approval is not permanent. A short routine for tracking approved extensions and plugins over time.
Spack CI signs package metadata with GPG keys in two classes. Only the public facing Reputational Key should be used to verify package integrity.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.