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.

• fina

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/kierdavis/fina\.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.

  • Dependency dirs 3.0.1 is significantly outdated

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

    dirs versions

  • Dependency itertools 0.9 is significantly outdated

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

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

    itertools versions

  • Dependency clap 2.33.3 is outdated

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

    clap versions

  • Dependency lalrpop 0.19.0 is outdated

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

    lalrpop versions

  • Dependency lalrpop-util 0.19.0 is outdated

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

    lalrpop-util versions

  • Dependency toml 0.5.7 is outdated

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

    toml 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

• sakaagari

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/kierdavis/sakaagari\.git

  • Dependency git2 0.13.12 is outdated

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

    git2 versions

  • Dependency toml 0.5.7 is 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 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

• sakaagari, fina, charly, inara

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

• charly

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

• inara

  • Crate is 'reserved'

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

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