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.

• seahash

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

    It's an opportunity to update it to the current Rust edition.

    Maintenance status field docs

  • Missing categories

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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.33, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• cbloom

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["concurrency", "data-structures"] to the Cargo.toml.

    List of available categories

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.34, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• little-endian, eudex, speck, thread-object, control-flow, conc, io-error, zfs, plru

  • 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

• little-endian

  • Missing categories

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

    List of available categories

• little-endian, eudex, thread-object, io-error, zfs, plru

  • Latest stable release is old

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

• speck, control-flow, conc

  • Latest stable release is old

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

• conc

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency rand 0.3 is significantly outdated

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

    rand versions

  • Dependency spin 0.4 is significantly outdated

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

    spin versions

  • Missing categories

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

    List of available categories

• chashmap

  • Dependency owning_ref 0.3 has issues

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

    owning_ref crate

  • Dependency parking_lot 0.4 is significantly outdated

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

    parking_lot versions

  • Latest stable release is old

    It's been over 7 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 = ["concurrency"] to the Cargo.toml.

    List of available categories

• little-endian, speck, thread-object, control-flow, conc, io-error, zfs

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

• thread-object, conc, plru

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

• lz4-compress

  • Reported security advisory RUSTSEC-2017-0007

    lz4-compress is unmaintained

    All crate audits

  • Dependency byteorder 0.5 is significantly outdated

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

    byteorder versions

  • Dependency quick-error 1 is outdated

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

    quick-error versions

  • Missing categories

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

    List of available categories

• zfs

  • README missing from the repository

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

  • Missing categories

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

    List of available categories

• termion

  • Dependency numtoa 0.2.4 is outdated

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

    numtoa versions

  • Missing categories

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

    List of available categories

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.66, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• secbox

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rust-patterns", "security"] to the Cargo.toml.

    List of available categories

• type-name, diehardest, secbox, lz4-compress, extra, cake, prob

  • Latest stable release is old

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

• diehardest

  • Missing categories

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

    List of available categories

• eudex

  • Missing categories

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

    List of available categories

• thread-object

  • Missing categories

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

    List of available categories

• control-flow

  • Missing categories

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

    List of available categories

• type-name

  • Could not fetch repository

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

  • Missing categories

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

    List of available categories

• type-name, diehardest, secbox, lz4-compress, extra, cake, prob, concurrent

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

    More info

• type-name, lz4-compress, concurrent

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

• secbox, extra, concurrent

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Detecting docs.rs

• concurrent

  • Latest stable release is old

    It's been over 8 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 lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency rand 0.3 is significantly outdated

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

    rand versions

  • Dependency spin 0.4 is significantly outdated

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

    spin versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["tfs", "redox", "filesystem", "conc", "redox-fs"] (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.

• io-error

  • Missing categories

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

    List of available categories

• cake

  • Dependency rayon 0.4 is significantly outdated

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

    rayon versions

  • Missing categories

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

    List of available categories

• plru

  • Missing categories

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

    List of available categories

• extra

  • Missing categories

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

    List of available categories

• prob

  • Dependency num 0.1 is significantly outdated

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

    num versions

  • Missing categories

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

    List of available categories

• mlcr

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/mlcr ) failed. Please try again later.

• ralloc

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/ralloc ) failed. Please try again later.

• ralloc_shim

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/ralloc_shim ) failed. Please try again later.

• playpen

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/playpen ) failed. Please try again later.

• mars2

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/mars2 ) failed. Please try again later.

• rugra

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/rugra ) failed. Please try again later.

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