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.

• convert

  • Dependency curl 0.2.11 is significantly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    curl versions

  • Dependency env_logger 0.4.3 is significantly outdated

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

    env_logger versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency json 0.11.13 is significantly outdated

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

    json versions

  • Dependency log 0.3.8 is significantly outdated

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

    log versions

  • Dependency serde_json 0.6.0 is significantly outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    serde_json versions

  • 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

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

    More info

  • Dependency clap 2.26.0 is outdated

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

    clap versions

• plutus

  • Dependency curl 0.2.11 is significantly outdated

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

    curl versions

  • Dependency env_logger 0.4.3 is significantly outdated

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

    env_logger versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency json 0.11.13 is significantly outdated

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

    json versions

  • Dependency log 0.3.8 is significantly outdated

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

    log versions

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

    Maintenance status field docs

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

    More info

  • Dependency clap 2.26.0 is outdated

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

    clap versions

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