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.

• c-at-e-file-server-cli

  • Latest prerelease is old

    It's been over 2 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 toml_edit 0.14.4 is significantly outdated

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

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

    toml_edit versions

  • Dependency base64 0.13.0 is outdated

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

    base64 versions

  • Dependency fastly-api 1.0.0-beta.0 is slightly outdated

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

    fastly-api versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency simple-error 0.2.3 is outdated

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

    simple-error versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing keywords

    Help users find your crates. Add keywords = ["file-server", "c-at-e-file-server-cli", "cli", "upload", "local"] (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.

• compute-file-server-cli

  • Dependency toml_edit 0.14.4 is significantly outdated

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

    toml_edit versions

  • Dependency base64 0.13.0 is outdated

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

    base64 versions

  • Dependency fastly-api 1.0.0-beta.0 is slightly outdated

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

    fastly-api versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency simple-error 0.2.3 is outdated

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

    simple-error versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • Missing keywords

    Help users find your crates. Add keywords = ["compute-file-server-cli", "file-server", "cli", "upload", "local"] (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.

• compute-file-server-cli, c-at-e-file-server, c-at-e-file-server-cli, compute-file-server

  • Missing categories

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

• c-at-e-file-server

  • Latest prerelease is old

    It's been over 2 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

  • Dependency fastly 0.8.7 is outdated

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

    fastly versions

  • Dependency http 0.2.8 is outdated

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

    http versions

  • Missing keywords

    Help users find your crates. Add keywords = ["c-at-e-file-server", "file", "file-server", "compute-file-server", "done"] (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.

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

• trash-it

  • Dependency trash 1.2.0 is significantly outdated

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

    trash versions

  • Dependency clap 2.33.3 is outdated

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

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

    Maintenance status field docs

• compute-file-server

  • Dependency fastly 0.8.7 is outdated

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

    fastly versions

  • Dependency http 0.2.8 is outdated

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

    http versions

  • Missing keywords

    Help users find your crates. Add keywords = ["compute-file-server", "file-server", "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.

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