A package registry token leaked: what should you check and revoke?
Revoke the token, list recent publishes, check who has access and look for new versions you did not release. A checklist for npm and PyPI tokens.
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.
Revoke the token, list recent publishes, check who has access and look for new versions you did not release. A checklist for npm and PyPI tokens.
An old last commit does not always mean abandoned. Here is how to tell finished software from neglected software, and when to plan a replacement.
CISA notes tie 77 KEV entries to open source, third-party libraries or shared protocols, led by the Linux kernel. What dependency owners should do.
Pinning a digest stops surprise changes but also stops fixes. Automate update pull requests, review them, and rebuild on a schedule so pins stay fresh.
When a broker client library has an advisory, you need to know which services ship it. A short method for inventory, ownership and fast triage.
How ISO 27001 control 5.21 on the ICT supply chain applies to libraries and software suppliers, and what risk records an auditor expects to see.
Bundler loaders run in Node.js with full access to the build machine. Treat each as production code: review it, pin it and limit what the build can reach.
Before you evaluate a library, confirm it is the real one. Check links both ways between docs, repository and registry, and watch for similar names.
Log4j 1.x reached end of life on 5 August 2015 and known issues will not be fixed. See how to find it hiding in your Java apps and how to replace it.
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.