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.

• serde-query

  • Optional dependency 'serde-query-derive' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'serde-query-derive' may have been unintentional.

    Crate features

• sion-rs

  • Dependency base64 0.9 is significantly outdated

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

    base64 versions

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency ordered-float 0.5 is significantly outdated

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

    ordered-float versions

  • Dependency try_from is not needed

    try_from is in the standard library

    try_from crate

  • Latest stable release is old

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

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["encoding"] 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 = ["serializer-deserializer", "sion-rs", "sion"] (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.

• eff

  • Dependency crossbeam-channel 0.4.0 is significantly outdated

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

    crossbeam-channel versions

  • Dependency pin-project 0.4.5 is significantly outdated

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

    pin-project versions

  • Dependency proc-macro-hack 0.5.11 has issues

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

    proc-macro-hack crate

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["algorithms"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["eff", "computation", "context"] (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.

• task_scope

  • Dependency async-std 1.4.0 has issues

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

    async-std crate

  • Dependency bytes 0.5.3 is significantly outdated

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

    bytes versions

  • Dependency futures-intrusive 0.2.2 is significantly outdated

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

    futures-intrusive versions

  • Dependency parking_lot 0.9.0 is significantly outdated

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

    parking_lot versions

  • Dependency pin-project 0.4.6 is significantly outdated

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

    pin-project versions

  • Dependency tokio 0.2.6 has issues

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

    tokio crate

  • Missing keywords

    Help users find your crates. Add keywords = ["scope", "spawning", "cancellation", "runtime-agnostic", "harmful"] (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.

• eff, task_scope, eff-attr

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

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

    Maintenance status field docs

• fs-tracing

  • Dependency tracing-error 0.1.2 is significantly outdated

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

    tracing-error 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["filesystem"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["error", "fs-tracing", "tracing", "html"] (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.

• cargo-nix

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

    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

  • README missing from the repository

    We've searched https://github\.com/pandaman64/cargo\-nix\.git and could not find a README file there.

  • Dependency bstr 0.2.14 is significantly outdated

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

    bstr versions

  • Dependency clap 3.0.0-beta.2 is significantly outdated

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

    clap versions

  • Dependency color-eyre 0.5.10 is significantly outdated

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

    color-eyre versions

  • Dependency tracing-error 0.1.2 is significantly outdated

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

    tracing-error versions

  • Dependency tracing-subscriber 0.2.15 is significantly outdated

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

    tracing-subscriber versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/pandaman64/cargo-nix.git 60e2366d14db26f4c78040690c4c69bd67932d13.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Dependency ureq 2.0.1 is a bit outdated

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

    ureq versions

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• serde-query-core

  • Dependency syn 1.0.107 is significantly outdated

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

    syn versions

  • Dependency logos 0.12.1 is outdated

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

    logos versions

• serde-query-core, cargo-nix, serde-query-derive, eff-attr, unita

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

• eff-attr

  • Dependency proc-macro-hack 0.5.11 has issues

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

    proc-macro-hack crate

  • Dependency syn 1.0.8 is significantly outdated

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

    syn versions

• serde-query-derive

  • Dependency syn 1.0.107 is significantly outdated

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

    syn versions

• unita

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

  • README missing from the repository

    We've searched https://github\.com/pandaman64/unita\.git and could not find a README file there.

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