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.
birli
Dependency clap ~3.1.8 is significantly outdated
Upgrade to 4.5.37 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 derive_builder 0.11.1 is significantly outdated
Upgrade to 0.20.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 indicatif =0.17.8 is significantly outdated
Upgrade to 0.17.11 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version indicatif =0.17.8
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.
Dependency built ~0.7 is a bit outdated
Consider upgrading to 0.8.0 to get all the fixes and improvements.
Dependency env_logger 0.10.0 is outdated
Upgrade to 0.11.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.0 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Optional dependency 'prettytable-rs' 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 'prettytable-rs', 'clap', 'env_logger', 'shlex' may have been unintentional.
mwa_hyperbeam
Dependency cbindgen 0.25.0 is significantly outdated
Upgrade to 0.28.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pyo3 0.22.0 is significantly outdated
Upgrade to 0.24.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency hdf5-metno 0.9.2 is slightly outdated
Consider upgrading to 0.10.1 to get all the fixes and improvements.
Dependency hdf5-metno-sys 0.9.1 is outdated
Upgrade to 0.10.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency numpy 0.22.1 is outdated
Upgrade to 0.24.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.2 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["science"]
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 = ["mwa", "mwa-hyperbeam", "python", "hyperbeam", "hip"]
(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.Optional dependency 'cc' 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 'cc', 'cuda-runtime-sys', 'hip-sys', 'numpy', 'hdf5-metno-sys', 'pyo3' may have been unintentional.
mwa_giant_squid
Dependency built =0.7.6 is significantly outdated
Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clap ~4.4 is significantly outdated
Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency litemap =0.7.4 is significantly outdated
Upgrade to 0.7.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency reqwest =0.12.12 is significantly outdated
Upgrade to 0.12.15 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency sha-1 ~0.10 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency zerofrom =0.1.5 is significantly outdated
Upgrade to 0.1.6 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version built =0.7.6
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 litemap =0.7.4
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 reqwest =0.12.12
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 reqwest-retry =0.7.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.
Locked dependency version reqwest_cookie_store =0.8.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.
Locked dependency version zerofrom =0.1.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.
Dependency bytesize 1.3 is slightly outdated
Consider upgrading to 2.0.1 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["cryptography"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["mwa", "sha-1", "tar", "jobs", "client"]
(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.Optional dependency 'reqwest-retry' 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 'reqwest-retry', 'indicatif-log-bridge', 'anyhow', 'clap', 'simplelog', 'task-local-extensions', 'indicatif' may have been unintentional.
marlu
Dependency built =0.7.3 is significantly outdated
Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version built =0.7.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.
Dependency hifitime 3.6.0 is outdated
Upgrade to 4.0.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.10.0 is outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency rubbl_casatables 0.8.0 is slightly outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Dependency thiserror 1.0.0 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Optional dependency 'fitsio' 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 'fitsio', 'flate2', 'fitsio-sys', 'rubbl_casatables' may have been unintentional.
mwalib
Dependency built =0.7.3 is significantly outdated
Upgrade to 0.8.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency clap ~4.1 is significantly outdated
Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Locked dependency version built =0.7.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.
Dependency cbindgen ~0.26 is outdated
Upgrade to 0.28.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency env_logger ~0.10 is outdated
Upgrade to 0.11.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency numpy ~0.23 is outdated
Upgrade to 0.24.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pyo3 ~0.23 is outdated
Upgrade to 0.24.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency pyo3-stub-gen ~0.6 is a bit outdated
Consider upgrading to 0.8.2 to get all the fixes and improvements.
Dependency pyo3-stub-gen-derive ~0.6 is a bit outdated
Consider upgrading to 0.8.2 to get all the fixes and improvements.
Dependency thiserror 1.0 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Optional dependency 'ndarray' 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 'ndarray', 'anyhow', 'clap', 'env_logger', 'numpy', 'pyo3-stub-gen', 'pyo3-stub-gen-derive', 'pyo3' may have been unintentional.
mwa_hyperdrive
Dependency clap 3.1.0 is significantly outdated
Upgrade to 4.5.37 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency is-terminal is not needed
IsTerminal trait is in the standard library
Dependency serde_yaml 0.9.21 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency toml 0.7.2 is significantly outdated
Upgrade to 0.8.22 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency vec1 ~1.10.0 is significantly outdated
Upgrade to 1.12.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency built ~0.7 is a bit outdated
Consider upgrading to 0.8.0 to get all the fixes and improvements.
Dependency env_logger 0.10.0 is outdated
Upgrade to 0.11.8 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency hifitime 3.8.2 is outdated
Upgrade to 4.0.2 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency indexmap 1.8.0 is outdated
Upgrade to 2.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency itertools 0.10.0 is outdated
Upgrade to 0.14.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency strum 0.24.0 is outdated
Upgrade to 0.27.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency strum_macros 0.24.0 is outdated
Upgrade to 0.27.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency thiserror 1.0.7 is a bit outdated
Consider upgrading to 2.0.12 to get all the fixes and improvements.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["mathematics"]
to theCargo.toml
.Missing keywords
Help users find your crates. Add
keywords = ["telescope", "mwa", "component", "cuda", "radio-astronomy"]
(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.Optional dependency 'cc' 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 'cc', 'cuda-runtime-sys', 'hip-sys', 'plotters' may have been unintentional.
pal-sys
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["…"]
to theCargo.toml
.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.Dependency autotools 0 has issues
It may not be actively developed any more. Consider changing the dependency.
Dependency bindgen 0.58.1 is significantly outdated
Upgrade to 0.71.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement autotools = 0
Cargo does not always pick latest versions of dependencies! Specify the version as
autotools = "0.2.7"
. 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.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.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 keywords
Help users find your crates. Add
keywords = ["pal-sys", "pal", "rust-pal"]
(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.Published crate contains binary files
The crate contains binary files (autotools obfuscated code, obscure autoconf code). 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.
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.
aoflagger_sys
Using outdated edition for no reason
We estimate that this crate requires at least Rust 1.63, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run
cargo fix --edition
and updateedition="…"
inCargo.toml
.Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all 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
.