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.
oid
Latest stable release is old
It's been over 4 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?
isoflux
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
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.
No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.No readme property
Specify path to a
README
file for the project, so that information about is included in the crates.io tarball.Missing keywords
Help users find your crates. Add
keywords = ["cqrs", "responsibility", "es", "sourcing", "framework"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
bme280
Dependency derive_more 0.99.17 is outdated
Consider upgrading to 1.0.0 to get all the fixes and improvements.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Incorrect category
Crate's categories property in
Cargo.toml
contains 'embedded-hal', which isn't a category we recognizelib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.
Optional dependency 'defmt' exposed as an implicit feature
Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using
dep:
syntax. Features 'defmt', 'embedded-hal-async', 'derive_more' may have been unintentional.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.62, 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.
isoflux-core
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.No repository property
Specify git repository URL in
Cargo.toml
to help users find more information, contribute, and for lib.rs to read more info.No readme property
Specify path to a
README
file for the project, so that information about is included in the crates.io tarball.Missing keywords
Help users find your crates. Add
keywords = ["events", "cqrs", "sourcing", "shared", "es"]
(up to 5) to theCargo.toml
. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.
hvac, thermostat, rusty-pager, cryptonomicon
Latest stable release is old
It's been over 6 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"
).
freetsa
Dependency reqwest 0.11.12 is outdated
Upgrade to 0.12.12 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 thiserror 1.0.37 is a bit outdated
Consider upgrading to 2.0.11 to get all the fixes and improvements.
Optional dependency 'sha2' exposed as an implicit feature
Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using
dep:
syntax. Features 'sha2', 'tokio', 'clap' may have been unintentional.
rusty-pager
Dependency error-chain 0.11.0 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency reqwest 0.8.5 is significantly outdated
Upgrade to 0.12.12 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency uuid 0.6.3 is significantly outdated
Upgrade to 1.12.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.62, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.
thermostat, rusty-pager, cryptonomicon
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.
semver-util
Dependency strum 0.24.1 is outdated
Consider upgrading to 0.26.3 to get all the fixes and improvements.
cryptonomicon
Dependency ed25519-dalek 0.6.2 is significantly outdated
Upgrade to 2.1.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency error-chain 0.11.0 has issues
It may not be actively developed any more. Consider changing the dependency.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.