Ecosystem · Rust · Cargo
Vulnerabilities in your crates, read from Cargo.lock.
LibWatch reads Cargo.toml and Cargo.lock, checks every crate against known vulnerabilities and tracks the declared minimum Rust version.
What LibWatch reads in the repository
Cargo.tomlCargo.lock
Language version: rust-version in Cargo.toml
Nothing else: no cloning, no code run.
What LibWatch checks
The crates, and the Rust version
crates.io packages
Known vulnerabilities
Every package in the lockfile checked against OSV, which includes GitHub advisories.
Rust version
End of life
The declared version is tracked: you know when it stops getting fixes.
Health
License policy
Licenses that conflict with your project's policy are flagged.
An alert, in practice
A vulnerability in a crate, with the version that fixes it
The vulnerabilities that affect your versions, with the fixed version. Nothing more.
Real severity
CVSS severity and presence in the CISA KEV catalog
What to do
The fixed version, and the affected project
Where
Email, Slack, Zulip or webhook, set per project
calc-engine · Rust
Example · analysis from October 22
-
Outdated
rust-version
1.74
-
Medium severity
h2
0.3.24
-
Up to date
tokio
1.40.0
Rechecked every night at 2 a.m.
Tracked versions
Rust only fixes its latest stable release: LibWatch flags a rust-version that is far behind.
- Cargo.toml · rust-version
- Cargo.lock
Get started
Your first report in a few minutes
No pipeline to change.
Connect GitHub or GitLab
Self-hosted GitLab instances included.
Choose your Rust repositories
LibWatch finds the files listed above on its own, even in a monorepo.
Read the report, set up alerts
Exploited vulnerabilities first, fixed versions, language end of life.
Frequently asked questions
LibWatch and Rust
Do I need to install anything in the project?
No. LibWatch reads dependency files through the GitHub or GitLab API, without adding anything to your pipeline.
Are private registries supported?
Yes. A package from a private registry is identified as such: its name is never sent to a third-party service, and it stays in the project's inventory.
Does LibWatch detect the version installed on the server?
No. LibWatch reads the version declared in the repository (version file, lockfile or manifest). It has no access to your servers.