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.

• rptree

  • 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 colored 2.0.0 is a bit outdated

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

    colored versions

  • Missing keywords

    Help users find your crates. Add keywords = ["directory", "rptree", "root-directory", "command-line"] (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.

• playrs

  • 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

  • Dependency reqwest 0.11 is outdated

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

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

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

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["playrs", "file", "backtrace", "playground"] (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.

• dll

  • Failed to verify create's content against its repository

    Verified 8 out of 10 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 835477ab2647d800706931d62bc2d1d7d1cc057c, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.1.0'.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock does not match the repository.
    • .github/workflows/
      • release.yaml not found.
      • build.yaml does not match the repository.

    Fetched https://github.com/night-cruise/dll-rs.git tagged v0.1.0 (37e28ca9955d0e733ebd0549158d9a864500b234).

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Dependency zip 0.6.6 is outdated

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

    zip versions

  • Missing keywords

    Help users find your crates. Add keywords = ["command", "dll", "dll-rs"] (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.