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.
home
Missing categories
Categories improve browsing of lib.rs and crates.io. Add categories = ["os"] to the Cargo.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 = ["package-manager", "home", "cargo", "match", "standard-library"] (up to 5) to the Cargo.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.
marked-yaml
Dependency linked-hash-map =0.5.3 is significantly outdated
Upgrade to 0.5.6 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.
Locked dependency version linked-hash-map =0.5.3
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.
Locked dependency version yaml-rust =0.4.5
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.
Latest stable release is old
It's been over 23 months. How did the experiment go? 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?
subplot
Imprecise dependency requirement anyhow = 1
Cargo does not always pick latest versions of dependencies! Specify the version as anyhow = "1.0.75". If Cargo.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 minimal-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.
Imprecise dependency requirement thiserror = 1
Cargo does not always pick latest versions of dependencies! Specify the version as thiserror = "1.0.47". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add categories = ["embedded", "text-processing"] to the Cargo.toml.
Missing keywords
Help users find your crates. Add keywords = ["pattern", "embedded", "markup", "parser", "parses"] (up to 5) to the Cargo.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.
Imprecise dependency requirement clap = 4
Cargo does not always pick latest versions of dependencies! Specify the version as clap = "4.4.0". If Cargo.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 minimal-versions flag, 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-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.
Imprecise dependency requirement lazy_static = 1
Cargo does not always pick latest versions of dependencies! Specify the version as lazy_static = "1.4.0". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
Imprecise dependency requirement regex = 1
Cargo does not always pick latest versions of dependencies! Specify the version as regex = "1.9.0". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
Imprecise dependency requirement walkdir = 2
Cargo does not always pick latest versions of dependencies! Specify the version as walkdir = "2.3.0". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
git-testament
Missing categories
Categories improve browsing of lib.rs and crates.io. Add categories = […] to the Cargo.toml.
Missing keywords
Help users find your crates. Add keywords = ["testament", "git", "reproducible-builds"] (up to 5) to the Cargo.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.
subplotlib
Dependency state 0.5 is 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 = ["filesystem"] to the Cargo.toml.
Missing keywords
Help users find your crates. Add keywords = ["file", "step", "regex", "stdout", "stderr"] (up to 5) to the Cargo.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.
Imprecise dependency requirement lazy_static = 1
Cargo does not always pick latest versions of dependencies! Specify the version as lazy_static = "1.4.0". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
subplotlib, subplot-build, subplotlib-derive
README missing from crate tarball
Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.
pandoc
Dependency itertools 0.8 is significantly outdated
Upgrade to 0.11.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
License MIT/Apache-2.0 is not in SPDX syntax
Use "OR" instead of "/".
enumber
Dependency syn 1 is outdated
Upgrade to 2.0.29 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade; Also check out Dependabot service on GitHub.
Imprecise dependency requirement syn = 1
Cargo does not always pick latest versions of dependencies! Specify the version as syn = "2.0.29". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
Latest stable release is old
It's been over 2 years. How did the experiment go? Make a new release, either to refresh it, or to set [badges.maintenance] status = "deprecated" (or "as-is", "passively-maintained").
effective-limits
Dependency cfg-if 0.1.10 is significantly outdated
Upgrade to 1.0.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
subplot-build
Missing categories
Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools"] to the Cargo.toml.
Missing keywords
Help users find your crates. Add keywords = ["build", "buildrs", "codegen", "software-development", "short"] (up to 5) to the Cargo.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.
pikchr-cli, pandoc
Missing categories
Categories improve browsing of lib.rs and crates.io. Add categories = ["text-processing"] to the Cargo.toml.
pikchr
Missing categories
Categories improve browsing of lib.rs and crates.io. Add categories = ["visualization"] to the Cargo.toml.
subplotlib-derive
Imprecise dependency requirement syn = 2
Cargo does not always pick latest versions of dependencies! Specify the version as syn = "2.0.29". If Cargo.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 minimal-versions flag, used by users of old Rust versions.
git-testament-derive
Dependency syn 1.0 is outdated
Upgrade to 2.0.29 to get all the fixes, and avoid causing duplicate dependencies in projects.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.