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.

• cifra

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

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

    Maintenance status field docs

  • Dependency clap 3.0.0-rc.5 is significantly outdated

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

    clap versions

  • Dependency error-chain 0.12.2 has issues

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

    error-chain crate

  • Dependency rand 0.7.3 is significantly outdated

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

    rand versions

  • Dependency strum 0.21.0 is significantly outdated

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

    strum versions

  • Dependency strum_macros 0.21.1 is significantly outdated

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

    strum_macros versions

  • Dependency diesel 1.4.3 is outdated

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

    diesel versions

  • Dependency diesel_migrations 1.4.0 is outdated

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

    diesel_migrations versions

  • Dependency dirs 4.0 is outdated

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

    dirs versions

• steganer

  • Latest prerelease is old

    It's been over 5 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").

    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

  • Dependency error-chain 0.12.1 has issues

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

    error-chain crate

  • Dependency image 0.21.0 is significantly outdated

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

    image versions

  • Dependency pyo3 0.7.0 is significantly outdated

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

    pyo3 versions

  • 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.33.0 is outdated

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

    clap versions

  • Dependency num 0.2.0 is outdated

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

    num versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["multimedia::images"] 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 = ["steganography", "hiding", "hidden", "byte", "extract"] (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.

• steganer, cifra, test_common

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

• test_common

  • Dependency rand 0.7.3 is significantly outdated

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

    rand versions

  • Dependency ring 0.14.6 is significantly outdated

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

    ring versions

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

    Maintenance status field docs

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::testing"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["testing", "random", "system", "unit-testing", "integration"] (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.