crates.io Ships Security Tab and Tightens Publishing Controls
crates.io adds a Security tab backed by RustSec advisories and narrows trusted publishing paths to reduce common CI publishing risks.
- Sarah Gooding

crates.io has rolled out a set of changes that bring security information closer to the moment Rust developers choose dependencies, while quietly tightening some of the riskiest paths used to publish new crate versions.
The update introduces a new Security tab on crate pages backed by RustSec advisories, expands Trusted Publishing to additional CI systems, and removes support for GitHub Actions triggers that have been repeatedly implicated in CI compromise. It also adds new visibility into dependency risk and removes some of the most failure-prone publishing paths, without introducing more registry-level enforcement.
Security Advisories, Now Visible on Crate Pages
#Crate pages on crates.io now include a Security tab that displays known vulnerabilities affecting the selected version, using data from the RustSec advisory database. The tab lists advisories along with affected version ranges and links to additional details.

The feature builds directly on a Rust RFC proposed in late 2025, which argued that crates.io is where dependency decisions often happen informally, long before teams run audits or enforce policy in CI. By placing advisory information directly in the registry UI, crates.io makes known vulnerabilities visible at the point of dependency discovery, rather than assuming downstream tools will always catch them.
That differs from how vulnerability information typically enters workflows in other ecosystems. For example, on npm, security advisories are most often encountered after installation, through tools like npm audit or external scanners, rather than during package discovery itself. crates.io is instead treating vulnerability context as part of the selection process, not just a downstream check.
The implementation is deliberately limited in scope. The Security tab does not block installs, score crates, or attempt to summarize overall “security quality.” During the RFC discussion, maintainers raised concerns about advisory visibility turning into a reputational signal, particularly for widely used or long-maintained crates. The current design avoids that by focusing on security disclosures.
Crates.io Expands Trusted Publishing, with Narrower Defaults
#Alongside the Security tab, crates.io has continued expanding its Trusted Publishing support. Originally launched with GitHub Actions support, Trusted Publishing now also works with GitLab CI/CD, allowing maintainers to publish crates using OIDC-based authentication instead of long-lived API tokens. Support is currently limited to GitLab.com, though the crates.io team has refactored the implementation to make adding additional CI providers easier.
Crate owners can now also enable Trusted Publishing–only mode, which disables token-based publishing entirely for a crate. When enabled, new versions can only be published through approved CI workflows.
At the same time, crates.io has removed support for two GitHub Actions triggers, pull_request_target and workflow_run, from Trusted Publishing. Both triggers have been involved in past CI security incidents, where attackers exploited workflow permissions to escalate access or obtain publishing credentials. Rather than attempting to make every configuration safe, the registry is explicitly narrowing the set of supported publishing paths.
None of these controls are globally enforced. Maintainers can opt into stricter publishing, but crates.io is not mandating a single release model across the ecosystem.
Metadata and Infrastructure Changes
#The update also includes several changes aimed at improving the reliability of registry data.
- Publication timestamps in the crate index: Index entries now record when each version was published, allowing tools like Cargo and Renovate to determine release timing without additional API calls.
- Cleaner download statistics: Download counts now include only requests originating from Cargo, reducing distortion from bots, scrapers, and mirrors.
- Encrypted GitHub OAuth tokens: GitHub access tokens stored by crates.io are now encrypted at rest, and the legacy unencrypted storage has been removed.
- Source lines of code (SLOC) metrics: Crate pages now display SLOC counts calculated after publishing using the
tokeicrate, providing additional context during dependency selection.
Context From Safety-Critical Rust Adoption
#The impact of these changes is concentrated at the front of the dependency lifecycle, where crates are first evaluated and adopted.
In recent interviews conducted as part of the Rust Vision Doc process, engineers working in safety-critical domains described a common pattern: third-party crates are used heavily during early development and lower-criticality work, where speed and iteration matter most. As software moves toward certification and long-term support, those teams deliberately reduce their dependency surface, rewriting, internalizing, or tightly constraining external code to meet evidence and audit requirements.
That model explains why crates.io is focused on surfacing risk early. In those environments, dependency choices are expected to be revisited under pressure, and advisory visibility helps teams decide what to adopt or avoid before the cost of change becomes prohibitive.
For many Rust projects, however, dependencies chosen during discovery are never systematically revisited. Crates selected early often remain in production indefinitely, without a later hardening phase where they are replaced or narrowed. The new Security tab does not change how teams manage risk later in a project’s life, but it does change what is visible at the moment a dependency enters the supply chain.




