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.
symbolica
Dependency brotli 5.0 is significantly outdated
Upgrade to 8.0.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.Dependency rug =1.25.0 is significantly outdated
Upgrade to 1.27.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version rug =1.25.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.
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 is a bit outdated
Consider upgrading to 3.0.0 to get all the fixes and improvements.
Dependency pyo3 0.23 is outdated
Upgrade to 0.24.2 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 rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.1 to get all the fixes and improvements.
Dependency rand_xoshiro 0.6 is a bit outdated
Consider upgrading to 0.7.0 to get all the fixes and improvements.
Dependency tikv-jemallocator 0.5.4 is outdated
Upgrade to 0.6.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Optional dependency 'wolfram-library-link' exposed as an implicit feature
Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using
dep:syntax. Features 'wolfram-library-link', 'tikv-jemallocator', 'pyo3' may have been unintentional.
cuba, ecos-rs, scs-rs
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.
reform
Dependency crossbeam 0.4.1 is significantly outdated
Upgrade to 0.8.4 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency env_logger 0.5.4 is significantly outdated
Upgrade to 0.11.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency fastdivide 0.2.0 is significantly outdated
Upgrade to 0.4.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools ^0.7.7 is significantly outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency ndarray 0.12 is significantly outdated
Upgrade to 0.16.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pest ^1.0 is significantly outdated
Upgrade to 2.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pest_derive ^1.0 is significantly outdated
Upgrade to 2.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rand 0.5.4 is significantly outdated
Upgrade to 0.9.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
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").If the crate is truly stable, why not make a 1.0.0 release?
Dependency bitflags 1.0.4 is outdated
Upgrade to 2.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clap ^2.30.0 is outdated
Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency cpuprofiler 0.0.3 is outdated
Upgrade to 0.0.4 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency cpython ^0.2.1 is outdated
Upgrade to 0.7.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
cuba
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").
scs-rs
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").Published crate contains binary files
The crate contains binary files (ELF exe/lib, ELF lib, static library). 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.
ecos-rs
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").
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance] to their
status = "deprecated"Cargo.toml.