What is Rekor and what does a transparency log entry prove?
Rekor is Sigstore's append-only transparency log. An entry shows a signing event was recorded and can be audited, not that the signed software is safe.
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.
Rekor is Sigstore's append-only transparency log. An entry shows a signing event was recorded and can be audited, not that the signed software is safe.
minimumReleaseAge waits before installing new versions. trustPolicy no-downgrade refuses a version whose trust evidence got weaker. Two different checks.
Dependency hygiene for a polyglot team means the same four controls in every language: locked installs, integrity checks, update routine, shared inventory.
Dependency drift is when the packages in dev, staging, and prod no longer match. Here is how it starts, why it matters for security, and how to spot it.
builder.id names the build platform that produced an artifact, and SLSA says it alone determines the Build level. Learn what to trust and how to pin it.
Build cache poisoning plants a bad output where later builds will reuse it. Learn how it happens in shared caches, how to spot it and what to clear.
An SBOM management platform stores, validates, tracks and shares SBOMs across products and releases. Here is what that covers and what it does not.
A podling is a project still in Apache incubation. Incubation says governance is maturing, not that the code is unfinished or unsafe. How to judge one.
A poisoned update is malicious code shipped as a normal upgrade. A vulnerability is an accidental flaw. The difference changes how you detect and respond.
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.