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.
four-char-code
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["parser-implementations"]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.
Missing keywords
Help users find your crates. Add
keywords = ["ascii", "u32", "file-format", "represented", "byte-sequences"](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.
linux-sysno
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["os::unix-apis"]to theCargo.toml.
smc
README missing from the repository
We've searched
https://github\.com/shurizzle/rust\-smc\.gitand could not find a README file there.README missing from crate tarball
Cargo sometimes fails to package the
READMEfile. Ensure the path to theREADMEinCargo.tomlis 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.Dependency four-char-code 0.0.5 is outdated
Upgrade to 2.3.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.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?
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["os::macos-apis"]to theCargo.toml.
linux-stat, bsd-errnos
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]to theCargo.toml.
cc-args
Dependency bindgen 0.69.2 is significantly outdated
Upgrade to 0.72.1 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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["development-tools::build-utils"]to theCargo.toml.
linux-stat
Dependency linux-raw-sys 0.4.3 is significantly outdated
Upgrade to 0.12.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency linux-syscalls 0.3.1 is slightly outdated
Consider upgrading to 0.4.0 to get all the fixes and improvements.
linux-errnos
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["rust-patterns"]to theCargo.toml.
linux-raw-vdso
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["parser-implementations"]to theCargo.toml.Published crate contains binary files
The crate contains binary files (ELF lib). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.
launch-services
Dependency core-foundation 0.6.4 is significantly outdated
Upgrade to 0.10.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency core-foundation-sys 0.6.2 is significantly outdated
Upgrade to 0.8.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency bitflags 1.1.0 is outdated
Upgrade to 2.11.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 = ["os::macos-apis"]to theCargo.toml.Missing keywords
Help users find your crates. Add
keywords = ["macos-framework", "service", "incomplete", "launch"](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.
macos-spotify
Dependency four-char-code 0.0.3 is significantly outdated
Upgrade to 2.3.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 = ["multimedia::audio"]to theCargo.toml.Missing keywords
Help users find your crates. Add
keywords = ["events", "query", "spotify", "controlling", "apple"](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.
macos-spotify, launch-services, file-metadata-mditem-macros
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").
tokio-switching-sleep
Imprecise dependency requirement tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.52.0". IfCargo.lockends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using theminimal-versionsflag, used by users of old Rust versions.If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with
-Z minimal-versionsCargo option, because it's very easy to accidentally use a feature added in a later version.
tokio-switching-sleep, figfont, tokio-read-line
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").
figfont
Dependency bitflags 1.2.1 is outdated
Upgrade to 2.11.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.25 is outdated
Upgrade to 2.0.18 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency unicode-width 0.1.8 is outdated
Upgrade to 0.2.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency zip 0.5.12 is significantly outdated
Upgrade to 8.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Published crate contains binary files
The crate contains binary files (Zip file). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.
tokio-read-line
Dependency crossterm 0.19 is significantly outdated
Upgrade to 0.29.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency unicode-width 0.1 is outdated
Upgrade to 0.2.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
file-metadata-mditem-macros
Dependency quote 0.6.12 is significantly outdated
Upgrade to 1.0.45 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency syn 0.15.35 is significantly outdated
Upgrade to 2.0.117 to get all the fixes, and avoid causing duplicate dependencies in projects.
README missing from crate tarball
Cargo sometimes fails to package the
READMEfile. Ensure the path to theREADMEinCargo.tomlis valid, and points to a file inside the crate's directory.
linux-syscalls
Internal error
We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/linux-syscalls ) failed. Please try again later.
four-char-code-macros-impl
Internal error
We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/four-char-code-macros-impl ) failed. Please try again later.
macos-open
Internal error
We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/macos-open ) failed. Please try again later.
file-metadata
Internal error
We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/file-metadata ) failed. Please try again later.
No issues found in: apple-errnos
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.