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.
check_timed_logs_fast
Dependency memmap 0.5 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.
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.
Dependency fancy-regex 0.1.0 is significantly outdated
Upgrade to 0.14.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 glob 0.2.11 is significantly outdated
Upgrade to 0.3.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency time 0.1.40 is significantly outdated
Upgrade to 0.3.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
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.
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"
).If the crate is truly stable, why not make a 1.0.0 release?
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.24, which is newer than the last 2015-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.
ink_engine, ink, contract-metadata, contract-extrinsics, ink_ir, contract-build, ink_allocator, ink_env, ink_primitives, contract-transcode, ink_eth_compatibility, ink_codegen, ink_e2e, ink_storage, ink_prelude, ink_metadata, ink_storage_traits, ink_sandbox
Cryptocurrency crate
This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.
Author of this site is firmly convinced that cryptocurrencies have a net-negative effect on society.
ink_lang_ir, contract-analyze, ink_lang, ink_lang_codegen, ink_linting, ink_macro, ink_e2e_macro, ink_linting_utils, ink_linting_mandatory, ink_lang_macro, contract-info, ink_storage_derive, ink_alloc, ink_abi, ink_core, ink_abi_derive, ink_core_derive
Cryptocurrency crate
This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.
ink_memory
Crate is 'reserved'
Please be respectful of crates.io and don't squat crate names.
It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.
ink-cli
Internal error
We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/ink-cli ). Please try again later.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.