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.

• culper

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • 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 base64 0.9.2 is significantly outdated

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

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

    base64 versions

  • Dependency duct 0.11.1 is significantly outdated

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

    duct versions

  • Dependency error-chain 0.12.0 has issues

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

    error-chain crate

  • Dependency futures 0.1.25 has issues

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

    futures crate

  • Dependency parking_lot 0.6.4 is significantly outdated

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

    parking_lot versions

  • Dependency rand 0.6.1 is significantly outdated

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

    rand versions

  • Dependency reqwest 0.9.5 is significantly outdated

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

    reqwest versions

  • Dependency serde_yaml 0.7 has issues

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

    serde_yaml crate

  • Dependency toml 0.4.8 is significantly outdated

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

    toml versions

  • Dependency url 1.7.2 is significantly outdated

    Consider upgrading to 2.5.0 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.

    url versions

  • Dependency uuid 0.7 is significantly outdated

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

    uuid versions

  • Dependency clap 2.32.0 is outdated

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

    clap versions

  • Dependency dirs 1.0.4 is outdated

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

    dirs versions

  • Dependency rocket 0.4.0-rc.1 is outdated

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

    rocket versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["secret", "yaml", "encrypted", "gpg", "public-key"] (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.

• culper-lib

  • Missing categories

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

    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 base64 0.9.2 is significantly outdated

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

    base64 versions

  • Dependency failure 0.1.2 has issues

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

    failure crate

  • Dependency serde_yaml 0.7 has issues

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

    serde_yaml crate

  • Dependency toml 0.4.8 is significantly outdated

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

    toml versions

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

    Maintenance status field docs

  • Dependency dirs 1.0.4 is outdated

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

    dirs versions

  • Missing keywords

    Help users find your crates. Add keywords = ["shared", "culper", "culper-server"] (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.

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