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.
ethercat
Dependency memmap 0.7 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.
Dependency derive-new 0.5 is outdated
Upgrade to 0.7.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 thiserror 1.0 is a bit outdated
Consider upgrading to 2.0.12 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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["network-programming", "hardware-support"]
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.
ethercat, iter-read, serde-pickle, ads, ethercat-sys, mlzlog, ethercat-plc, mlzutil, fddf, ngc
License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
iter-read
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["rust-patterns"]
to theCargo.toml
.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.58, 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.
ethercat-sys
Dependency bindgen 0.63.0 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency regex =1.9.6 is significantly outdated
Upgrade to 1.11.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version regex =1.9.6
This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.
*-sys crate without links property
If this crate uses C libraries with public symbols, consider adding
links = "ethercat"
to crate'sCargo.toml
to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.
Dependency ioctl-sys 0.5.2 is outdated
Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Failed to verify create's content against its repository
Partially verified 9 files (includes 2 Cargo-generated).
- warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.3.1'.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
cargo update
.
- Create git tags after comitting any changes, and commit changes after bumping versions and running
Looked for the crate in
ethercat-sys/
. Fetchedhttps://github.com/ethercat-rs/ethercat.git
82d069fba5ad9f3159b1b7e98d0472a520e4506c.Checked on 2024-08-10
This check is experimental.
- warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.3.1'.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
mlzutil
README missing from the repository
We've searched
https://github\.com/birkenfeld/mlzutil\.git
and could not find a README file there.Dependency time =0.3.20 is significantly outdated
Upgrade to 0.3.41 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version time =0.3.20
This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.
No readme property
Specify path to a
README
file for the project, so that information about is included in the crates.io tarball.Dependency hostname 0.3.1 is a bit outdated
Consider upgrading to 0.4.1 to get all the fixes and improvements.
Dependency itertools 0.10.0 is outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Missing keywords
Help users find your crates. Add
keywords = ["mlzutil", "mlz"]
(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.
arexibo
Dependency base64ct ~1.6 is significantly outdated
Consider upgrading to 1.7.0 to get all the fixes and improvements.
Dependency time 0.3.37 is significantly outdated
Consider upgrading to 0.3.41 to get all the fixes and improvements.
Dependency nix 0.29 is outdated
Consider upgrading to 0.30.1 to get all the fixes and improvements.
Dependency rand 0.8 is a bit outdated
Consider upgrading to 0.9.1 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["gui"]
to theCargo.toml
.
mlzlog
Dependency ansi_term 0.12.1 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency hashbrown 0.13.0 is significantly outdated
Upgrade to 0.15.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency log4rs =1.2.0 is significantly outdated
Upgrade to 1.3.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version log4rs =1.2.0
This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.
ethercat-plc
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.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set
cfg()
flags just for docs.rs and use them to hide problematic code.
serde-pickle
Dependency criterion 0.4 is significantly 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 = ["encoding", "parser-implementations"]
to theCargo.toml
.Optional dependency 'criterion' exposed as an implicit feature
Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using
dep:
syntax. Feature 'criterion' may have been unintentional.Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.63, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.
ads, ethercat-sys, mlzlog, ethercat-plc, tango-client, mlzutil, ngc
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.
fddf
Dependency structopt 0.3.3 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.
Dependency blake3 0.3.1 is significantly outdated
Consider upgrading to 1.8.0 to get all the fixes and improvements.
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"
).Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["command-line-utilities", "filesystem"]
to theCargo.toml
.
ngc
Dependency fixedbitset 0.3 is significantly outdated
Upgrade to 0.5.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency strum 0.20 is significantly outdated
Upgrade to 0.27.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency strum_macros 0.20 is significantly outdated
Upgrade to 0.27.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.10 is outdated
Upgrade to 0.14.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?
ads
Dependency zerocopy 0.7.35 is significantly outdated
Upgrade to 0.8.25 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.13.0 is outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.63 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.63, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.
clippy_lints
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"
).Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.
Dependency cargo_metadata 0.5 is significantly outdated
Upgrade to 0.19.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency if_chain 0.1 is significantly outdated
Upgrade to 1.0.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.7 is significantly outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency matches is not needed
matches! macro in the standard library
Dependency pulldown-cmark 0.1 is significantly outdated
Upgrade to 0.13.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency regex-syntax 0.6 is significantly outdated
Upgrade to 0.8.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency toml 0.4 is significantly outdated
Upgrade to 0.8.22 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency url 1.7.0 is significantly outdated
Upgrade to 2.5.0 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.
docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
Dependency semver 0.9.0 is outdated
Upgrade to 1.0.26 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 = ["text-processing"]
to theCargo.toml
.
overload-strings
Latest stable release is old
It's been over 8 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 = ["…"]
to theCargo.toml
.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.
docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.Missing keywords
Help users find your crates. Add
keywords = ["overload-strings", "plugin", "overloading", "add"]
(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.
advtools
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.Dependency hashbrown 0.11.2 is significantly outdated
Upgrade to 0.15.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.10.1 is outdated
Upgrade to 0.14.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"
).License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.Missing keywords
Help users find your crates. Add
keywords = ["advtools", "moved", "search"]
(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.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
usecop
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.Dependency base64 0.21.5 is outdated
Upgrade to 0.22.1 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 = ["embedded"]
to theCargo.toml
.
tango-client-sys
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.*-sys crate without links property
If this crate uses C libraries with public symbols, consider adding
links = "tango-client"
to crate'sCargo.toml
to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.Missing keywords
Help users find your crates. Add
keywords = ["tango", "client", "tango-client-sys", "tango-rs"]
(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.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
pils
Failed to verify create's content against its repository
Verified 2 out of 4 files (includes 2 Cargo-generated).
- warning: The crates.io package has no commit hash associated with it.
- Publish a new version, without using
--allow-dirty
flag. Make sure all changes are committed before publishing. Useinclude
/exclude
inCargo.toml
to omit unnecessary files.
- Publish a new version, without using
- warning: The crates.io package has no information about its path inside its repository.
- warning: Could not discover crate's location in its repository (via tags).
- warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
- warning: There is no matching git tag containing version '0.0.0'.
- warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
Files in the crates.io crate compared to the repository:
Cargo.lock
not found.Cargo.toml.orig
does not match the repository.lib.rs
does not match the repository.
Fetched
https://github.com/birkenfeld/zapf-rs.git
04340ec7fdbc7c81a8f8168506bec4b128fa5fb1.Checked on 2025-04-12
- warning: The crates.io package has no commit hash associated with it.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.README missing from the repository
We've searched
https://github\.com/birkenfeld/zapf\-rs\.git
and could not find a README file there.No readme property
Specify path to a
README
file for the project, so that information about is included in the crates.io tarball.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.
secop
Dependency structopt 0.3.2 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.
Dependency clap 2.33.0 is outdated
Consider upgrading to 4.5.38 to get all the fixes and improvements.
Dependency daemonize 0.4.1 is outdated
Consider upgrading to 0.5.0 to get all the fixes and improvements.
Dependency mlzlog 0.7.0 is a bit outdated
Consider upgrading to 0.8.3 to get all the fixes and improvements.
Dependency mlzutil 0.2.0 is slightly outdated
Consider upgrading to 0.4.1 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["hardware-support"]
to theCargo.toml
.
tango-client
Dependency time 0.1.42 is significantly outdated
Upgrade to 0.3.41 to get all the fixes, and avoid causing duplicate dependencies in projects.
usecop-derive
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.
secop-modules
Dependency parking_lot 0.11.0 is significantly outdated
Upgrade to 0.12.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency mlzlog 0.7.0 is a bit outdated
Consider upgrading to 0.8.3 to get all the fixes and improvements.
Dependency mlzutil 0.2.0 is slightly outdated
Consider upgrading to 0.4.1 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["hardware-support"]
to theCargo.toml
.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
secop-core
Dependency hashbrown 0.11.2 is significantly outdated
Upgrade to 0.15.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency parking_lot 0.11.0 is significantly outdated
Upgrade to 0.12.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency base64 0.13.0 is outdated
Upgrade to 0.22.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency derive-new 0.5.8 is outdated
Upgrade to 0.7.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency mlzlog 0.7.0 is a bit outdated
Consider upgrading to 0.8.3 to get all the fixes and improvements.
Dependency mlzutil 0.2.0 is slightly outdated
Consider upgrading to 0.4.1 to get all the fixes and improvements.
Dependency toml 0.5.3 is outdated
Upgrade to 0.8.22 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 = ["hardware-support"]
to theCargo.toml
.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
ethercat-derive
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.Dependency syn 1.0 is significantly outdated
Upgrade to 2.0.101 to get all the fixes, and avoid causing duplicate dependencies in projects.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
secop-derive
Dependency darling 0.13.0 is significantly outdated
Upgrade to 0.20.11 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency syn 1.0.5 is significantly outdated
Upgrade to 2.0.101 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency synstructure 0.12.1 is significantly outdated
Upgrade to 0.13.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
clippy
Dependency term 0.5.1 is significantly outdated
Consider upgrading to 1.0.2 to get all the fixes and improvements.
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"
).License MIT/Apache-2.0 is not in SPDX syntax
Use
OR
instead of/
.
zapf
Crate contains junk files
The crate contains boilerplate Rust files with no real functionality.
README missing from the repository
We've searched
https://github\.com/birkenfeld/zapf\-rs\.git
and could not find a README file there.README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.
No issues found in: gr
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.