Lib.rs

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.

• fixnum

  • Locked dependency version i256 =0.1.1

    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.

    i256 versions

  • Dependency i256 =0.1.1 is outdated

    Upgrade to 0.2.4 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.

    i256 versions

  • Dependency schemars ^0.8 is outdated

    Upgrade to 1.2.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.

    schemars versions

  • Imprecise dependency requirement parity-scale-codec = ^3

    Cargo does not always pick latest versions of dependencies! Specify the version as parity-scale-codec = "3.7.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 the 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.

    parity-scale-codec versions

  • Optional dependency 'parity-scale-codec' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'parity-scale-codec' may have been unintentional.

    Crate features

• idr-ebr

  • Imprecise dependency requirement fastrand = ^2

    Cargo does not always pick latest versions of dependencies! Specify the version as fastrand = "2.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 the minimal-versions flag, used by users of old Rust versions.

    fastrand versions

• top-type-sizes

  • Dependency structopt ^0.3.26 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Imprecise dependency requirement serde = ^1

    Cargo does not always pick latest versions of dependencies! Specify the version as serde = "1.0.228". 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 the 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.

    serde versions

  • Dependency nom ^7.1.3 is a bit outdated

    Consider upgrading to 8.0.0 to get all the fixes and improvements.

    nom versions

• rscam, weighted-select, rate-limit-queue

  • 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").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• rate-limit-queue

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] 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.

    List of available categories

  • 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 delegate ^0.1.3 is significantly outdated

    Upgrade to 0.13.5 to get all the fixes, and avoid causing duplicate dependencies in projects.

    delegate versions

  • Missing keywords

    Help users find your crates. Add keywords = ["rate-limiting", "limit"] (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.

• rscam

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["multimedia::video"] to the Cargo.toml.

    List of available categories

• elfo-utils, weighted-select

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["asynchronous"] to the Cargo.toml.

    List of available categories

• elfo-macros-impl, elfo-macros

  • Latest prerelease is old

    It's been over 3 months. 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.

    Maintenance status field docs

• weighted-select

  • Dependency futures ^0.1.26 has issues

    It may not be actively developed any more. Consider changing the dependency.

    futures crate

• ridge

  • 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 the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• whizz

  • 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 the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• mandrel

  • 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 the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• elfo

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo ) failed. Please try again later.

• elfo-test

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-test ) failed. Please try again later.

• elfo-telemeter

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-telemeter ) failed. Please try again later.

• elfo-pinger

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-pinger ) failed. Please try again later.

• elfo-network

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-network ) failed. Please try again later.

• elfo-logger

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-logger ) failed. Please try again later.

• elfo-dumper

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-dumper ) failed. Please try again later.

• elfo-configurer

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-configurer ) failed. Please try again later.

• elfo-core

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/elfo-core ) failed. Please try again later.

• ch2rs

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/ch2rs ) failed. Please try again later.

• typed-clickhouse

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/typed-clickhouse ) failed. Please try again later.

If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.