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.
junkbox
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.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.Dependency ron 0.8.0 is outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
Missing keywords
Help users find your crates. Add
keywords = ["package", "declarative", "management", "package-management", "obvious"]
(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.
dust-lang
Dependency nu-ansi-term 0.49.0 is significantly outdated
Upgrade to 0.50.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reedline 0.28.0 is significantly outdated
Upgrade to 0.39.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
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 colored 2.1.0 is a bit outdated
Consider upgrading to 3.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.Dependency crossterm 0.27.0 is outdated
Upgrade to 0.28.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency enum-iterator 1.4.1 is outdated
Consider upgrading to 2.1.0 to get all the fixes and improvements.
Dependency env_logger 0.10 is outdated
Upgrade to 0.11.7 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency getrandom 0.2 is outdated
Consider upgrading to 0.3.2 to get all the fixes and improvements.
Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Dependency reqwest 0.11.20 is outdated
Upgrade to 0.12.15 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency tree-sitter 0.20.10 is outdated
Upgrade to 0.25.3 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 = ["compilers"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["programming-language", "concurrency", "dust", "safety", "management"]
(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.
serial_int
Imprecise dependency requirement serde = ^1
Cargo does not always pick latest versions of dependencies! Specify the version as
serde = "1.0.219"
. IfCargo.lock
ends 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-versions
flag, used by users of old Rust versions.This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.
expressive
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Missing keywords
Help users find your crates. Add
keywords = ["expression", "fork", "expression-parser", "evalexpr"]
(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.
tree-sitter-dust
Failed to verify create's content against its repository
Could not check any files
- warning: The crates.io package has no information about its path inside its repository.
- error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
- Make sure the
repository
URL inCargo.toml
is correct and works withgit clone
. The repository must be public.
- Make sure the
Checked on 2024-07-24
This check is experimental.
Dependency tree-sitter ~0.20.10 is outdated
Upgrade to 0.25.3 to get all the fixes, and avoid causing duplicate dependencies in projects.
fs_lib
Crate contains junk files
The crate contains boilerplate Rust files with no real functionality.
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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.