Is a git dependency in Cargo safe? Branch, tag and rev compared
How Cargo locks git dependencies, what branch, tag and rev each mean, and how to keep a git dependency reviewable and pinned to one commit hash.
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.
How Cargo locks git dependencies, what branch, tag and rev each mean, and how to keep a git dependency reviewable and pinned to one commit hash.
Use the cargo deny sources check to fail builds when a Rust crate comes from an unapproved registry or git repo. Keys, defaults and a safe rollout.
The cargo deny bans check blocks named crates, flags duplicate versions and wildcard requirements. Keys, defaults, skip options and a rollout plan.
The cargo deny advisories table controls yanked crates, unmaintained crates and ignores. Defaults, what each value does and a practical policy.
cargo audit can check a compiled binary with its bin subcommand. Accuracy depends on whether it was built with cargo auditable. What to expect.
A Sigstore bundle packs the certificate, signature and log evidence needed to verify later. What it contains, what it still needs, and how to test it.
Yes. CISA says VEX is designed to integrate with SBOMs but does not require one. See what you lose without an SBOM and how to name products instead.
No. npm, PyPI, Maven Central and crates.io treat a published version as permanent. What each one lets you do instead, and why that protects your builds.
Private versions can be deleted. Public ones only if under 5,000 downloads. Restore works for 30 days. What to do when you need a bad version gone.
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.