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.

• colori, gzip, gzip_cli

  • 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?

    Maintenance status field docs

• colori, gzip, gzip_cli

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

• gzip

  • Dependency crc 1.8 is significantly outdated

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

    crc versions

  • Dependency enumflags2 0.6.4 is significantly outdated

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

    enumflags2 versions

  • Dependency deflate 0.8 is outdated

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

    deflate versions

  • Imprecise dependency requirement byteorder = 1

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

    byteorder versions

• gzip_cli

  • Dependency structopt 0.3 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

  • Dependency indicatif 0.15 is significantly outdated

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

    indicatif versions

  • Imprecise dependency requirement colored = 2

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

    colored versions

• header

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/header ). Please try again later.

• body

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/body ). Please try again later.

• chakra

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/chakra ). Please try again later.

• dhcp

  • Internal error

    We couldn't check this crate at this time, because: Crate needed for the dashboard Origin( lib.rs/crates/dhcp ). 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.