Issues found
Based on crates you own that have been published to crates.io. The best way to monitor these issues is to subscribe to the atom feed in your RSS reader.
darklua
Dependency notify 7.0.0 is significantly outdated
Upgrade to 8.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Dependency serde_yaml 0.9.33 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency notify-debouncer-full 0.4.0 is outdated
Upgrade to 0.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Dependency petgraph 0.6.5 is a bit outdated
Consider upgrading to 0.7.1 to get all the fixes and improvements.
Dependency wax 0.5.0 is outdated
Upgrade to 0.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["games", "compilers"]
to theCargo.toml
.Even if there are no categories that fit precisely, pick one that is least bad. You can also propose new categories in crates.io issue tracker.
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.76, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.
create-roblox-project
Dependency structopt 0.3.21 has issues
It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.
The Cargo package has no git commit information
Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.
To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.
Dependency git2 0.13.17 is outdated
Upgrade to 0.20.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pretty_env_logger 0.4.0 is outdated
Upgrade to 0.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Latest stable release is old
It's been over 3 years. Is this crate still maintained? Make a new release, either to refresh it, or to set
[badges.maintenance] status = "deprecated"
(or
"as-is"
,"passively-maintained"
).If the crate is truly stable, why not make a 1.0.0 release?
lualexer
Latest stable release is old
It's been over 5 years. Is this crate still maintained? Make a new release, either to refresh it, or to set
[badges.maintenance] status = "deprecated"
(or
"as-is"
,"passively-maintained"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["parser-implementations"]
to theCargo.toml
.
luaparser
Latest stable release is old
It's been over 5 years. Is this crate still maintained? Make a new release, either to refresh it, or to set
[badges.maintenance] status = "deprecated"
(or
"as-is"
,"passively-maintained"
).Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["compilers"]
to theCargo.toml
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.