
Rust 1.100 ships on November 12 with a feature the ecosystem has needed for years: native dependency cooldowns in Cargo. The catch is that it ships opt-in. Upgrade Rust and nothing changes. Your projects stay as exposed to supply chain attacks as they were yesterday, unless you add three lines to a config file. Most teams won’t know that.
The Supply Chain Landscape That Made This Necessary
The numbers from 2026 are not good. Sonatype’s cumulative count of malicious open-source packages has crossed 1.2 million. This year alone saw 59 distinct supply chain campaigns. The analysis behind RFC 3923—the RFC that defines this feature—found that 8 of the 10 most prominent supply chain attacks had exploitation windows under seven days. Most malicious packages live for hours, not months. That’s the attack window this feature closes.
Last month’s LiteLLM compromise illustrates the threat clearly. Attackers registered a lookalike repository, used stolen engineer credentials to override branch protection, and published malicious wheels to PyPI. The package lived on PyPI for just a few hours but still reached 49,000 downloads. The payload stole SSH keys, cloud credentials, and AI API keys from every process that started—not just processes that imported LiteLLM. A cooldown wouldn’t have prevented the publish, but it would have stopped any project from automatically pulling in that version before researchers had time to flag it.
On crates.io specifically, an August 2026 attack on arrayref, internment, and append-only-vec saw malicious versions removed in under 90 minutes. The new Cargo cooldown would have blocked all three from entering any project configured with even a one-day minimum age.
How Cargo Cooldowns Work
The feature is called Minimum Publish Age. When the resolver selects dependency versions, it ignores any version younger than the configured threshold. If no older version satisfies the dependency constraint, resolution fails with an error—it does not silently fall back to the too-new version. Versions already recorded in Cargo.lock are exempt, so an existing working build won’t break when you upgrade Rust.
Configuration lives in .cargo/config.toml at the workspace or user level:
[registry]
global-min-publish-age = "7 days"
Cargo accepts any reasonable duration: "1 day", "72 hours", "2 weeks". The resolver.incompatible-publish-age setting defaults to "deny", so those two lines are all it takes. Commit this file to your repo root so everyone on the team and every CI pipeline picks it up automatically.
For urgent security patches where you need a package the moment it’s published, the override is a single environment variable:
CARGO_RESOLVER_INCOMPATIBLE_PUBLISH_AGE=allow cargo update -p some-crate --precise 1.2.3
The Opt-In Problem
This is the part most coverage glosses over. Cargo’s default minimum publish age is zero. Upgrading to Rust 1.100 the day it ships on November 12 does exactly nothing for your supply chain posture. The feature only helps if you configure it—per workspace, per machine, or system-wide. Teams that don’t know about it remain fully exposed.
The RFC is honest about this tradeoff: enabling the feature for everyone retroactively would silently break projects that depend on recently-published crates. The opt-in design is the right call. But it means the burden is on you to turn it on.
What It Doesn’t Cover
Be clear-eyed about the scope. The cooldown applies to the Cargo resolver for workspace builds. It does not apply to:
cargo install(standalone binary installs)- Git dependencies or local path dependencies
- Custom registries that don’t provide publish timestamps
- Versions already in
Cargo.lock—an existing compromised dependency won’t be removed retroactively
After enabling it, audit your Cargo.lock for recently-added entries and review them manually. The cooldown protects future dependency resolutions, not the current state of your lockfile.
What Else Is in Rust 1.100
The cooldown feature dominates the 1.100 story, but two other Cargo changes are worth noting. Cargo now emits an unused_dependencies lint when a dependency isn’t referenced by any target—a long-requested addition. Cargo also ships a new build directory layout for intermediate artifacts, which unblocks future artifact garbage collection for anyone who has watched their target/ folder consume tens of gigabytes. The wasm32-wasip3 target is promoted to Tier 2, gaining official builds and automated testing. See the full 1.100.0 changelog for the complete list of stabilizations.
Action Items
Rust 1.100 beta is available today. Stable lands November 12. Here’s what to do:
- Add
[registry] global-min-publish-age = "7 days"to.cargo/config.tomlin every workspace. - Commit that file to version control so CI and all teammates inherit the setting.
- Audit your current
Cargo.lockfor very recently added dependencies and review them manually. - Test the emergency override command in staging so your team knows how to use it when needed.
The protection is real. The attack window that makes supply chain attacks viable is exactly the window this feature closes. Socket.dev’s analysis of recent crates.io incidents shows the pattern clearly: short-lived malicious versions, automated adoption. Turn it on.

