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.
windres, w32-error, ggpo-sys
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").If the crate is truly stable, why not make a 1.0.0 release?
gcj-helper
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 clippy 0.0 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency rayon 0.6 is significantly outdated
Upgrade to 1.10.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 7 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 Apache-2.0/MIT is not in SPDX syntax
Use
ORinstead of/.
ng-log
Latest stable release is old
It's been over 9 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.
concat-string, find-winsdk, gcj-helper, ng-log, vswhere
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.
concat-string, find-winsdk, vswhere
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").It's an opportunity to update it to the current Rust edition.
find-winsdk
Dependency winreg 0.5 is significantly outdated
Upgrade to 0.55.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.
Imprecise dependency requirement serde = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
serde = "1.0.218". 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.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.
bsa3-hash
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").Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.
vswhere
Dependency url 1 is significantly outdated
Upgrade to 2.5.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement serde = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
serde = "1.0.218". 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.Dependency semver 0.9 is outdated
Upgrade to 1.0.26 to get all the fixes, and avoid causing duplicate dependencies in projects.
redshirt
Dependency ring ^0.16.0 is outdated
Upgrade to 0.17.12 to get all the fixes, and avoid causing duplicate dependencies in projects.
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").
ggpo-sys
Dependency bindgen ^0.53.0 is significantly outdated
Upgrade to 0.71.1 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.
No issues found in: slice-cast
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.