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.

• bankroll

  • 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 ansi_term 0.12.1 has issues

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

    ansi_term crate

  • Dependency monee 0.0.6 is slightly outdated

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

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

    monee versions

  • Dependency toml 0.5.6 is outdated

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

    toml versions

  • 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

  • Missing categories

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

• vivo

  • Published crate doesn't match its repository

    Partially verified 12 files (includes 2 Cargo-generated).

    Fetched https://codeberg.org/tuck/vivo 14d81fa44513ddb71d53a8e17dd4bf19350ed1be.

    Checked on 2024-09-22

    This check is experimental.

    Forum thread

  • Dependency colored 2.1 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

• monee

  • 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 = ["finance", "parser-implementations"] to the Cargo.toml.

    List of available categories

• comma-cli

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

• restic-rs

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

  • Could not fetch repository

    We've had trouble cloning git repo from https://gitlab\.com/dantuck/restic\-rs\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

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