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.

• zerocopy

  • Dependency itertools 0.11 is significantly outdated

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

    itertools versions

  • Dependency trybuild =1.0.89 is significantly outdated

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

    trybuild versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Optional dependency 'zerocopy-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 'zerocopy-derive' may have been unintentional.

    Crate features

• unsafe-fields

  • Published crate doesn't match its repository

    Verified 7 out of 8 files (includes 2 Cargo-generated).

    Files in the crates.io crate compared to the repository:

    • Cargo.toml.orig does not match the repository.

    Looked for the crate in unsafe-fields/. Fetched https://github.com/google/zerocopy.git tagged unsafe-fields-v0.2.1 (0fae530a5b2e0566064548ed59f4918d424fd01b).

    Checked on 2024-10-23

    This check is experimental.

    Forum thread

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rust-patterns"] 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 = ["unsafe", "fields", "invariants", "safety", "swapping"] (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.

• internet-checksum

  • Could not fetch repository

    We've had trouble cloning git repo from https://fuchsia\.googlesource\.com/fuchsia/+/HEAD/src/connectivity/lib/internet\-checksum

    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.

  • 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

• slab-alloc

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

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

    Maintenance status field docs

  • Dependency interpolate_idents 0.1 has issues

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

    interpolate_idents crate

  • 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.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.

    rand versions

  • 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

  • Dependency mmap-alloc 0.1.0 is slightly outdated

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

    mmap-alloc versions

  • Dependency object-alloc 0.1.0 is slightly outdated

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

    object-alloc versions

• object-alloc-test

  • 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

  • Dependency interpolate_idents 0.1 has issues

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

    interpolate_idents crate

  • 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 quickcheck 0.4 is significantly outdated

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

    quickcheck versions

  • Dependency rand 0.3 is significantly outdated

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

    rand versions

  • Dependency winapi 0.2 has issues

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

    winapi crate

  • 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

  • Dependency object-alloc 0.1.0 is slightly outdated

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

    object-alloc versions

  • Dependency twox-hash 1.1 is slightly outdated

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

    twox-hash versions

• mmap-alloc

  • 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

  • Dependency errno 0.2 is significantly outdated

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

    errno versions

  • Dependency kernel32-sys 0.2 has issues

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

    kernel32-sys crate

  • Dependency winapi 0.2 has issues

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

    winapi crate

  • Dependency object-alloc 0.1.0 is slightly outdated

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

    object-alloc versions

• mundane

  • Dependency goblin 0.0.24 is significantly outdated

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

    goblin versions

  • 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

  • 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

  • Published crate contains binary files

    The crate contains binary files (ELF exe/lib, Mach-o exe, static library). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.47, 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

• package-test-b3e120686354b35756b0

  • Missing categories

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

    List of available categories

  • README missing from the repository

    We've searched https://github\.com/joshlf/package\-test\.git and could not find a README file there.

  • 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

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

  • 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

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["package-test-b3e120686354b35756b0", "packaging", "test", "filesystem-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.

• alloc-tls, never, alloc-fmt

  • 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

• elfmalloc

  • 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

  • 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 log 0.3.8 is significantly outdated

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

    log versions

  • 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

  • Dependency mmap-alloc 0.1.0 is slightly outdated

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

    mmap-alloc versions

• const-unwrap-9dfd7e7b6ae4d549987171c9f89a823d

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

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

  • 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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["const", "unwrap", "options", "context", "experiment"] (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.

• packet-9dfd7e7b6ae4d549987171c9f89a823d

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

  • Dependency zerocopy =0.7.0-alpha.4 is significantly outdated

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

    zerocopy versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["byte-buffer", "packet", "serialization", "body", "packet-parser"] (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.

• internet-checksum, never, packet-9dfd7e7b6ae4d549987171c9f89a823d, mmap-alloc

  • 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

• internet-checksum, never, zerocopy-derive, packet-9dfd7e7b6ae4d549987171c9f89a823d

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

• object-alloc

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

    Maintenance status field docs

• malloc-bind

  • 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

  • Dependency errno 0.2 is significantly outdated

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

    errno versions

  • 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

  • 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

• bsalloc

  • 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

  • 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

  • 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

  • Dependency mmap-alloc 0.1.0 is slightly outdated

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

    mmap-alloc versions

• never

  • Could not fetch repository

    We've had trouble cloning git repo from https://fuchsia\.googlesource\.com/fuchsia/+/master/garnet/lib/rust/never

• zerocopy-derive

  • Could not fetch repository

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

• alloc-fmt

  • Dependency spin 0.4.6 is significantly outdated

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

    spin versions

  • Optional dependency 'backtrace' 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 'backtrace' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.76, 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

• bagpipe

  • Dependency crossbeam 0.2 is significantly outdated

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

    crossbeam 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

  • 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

• alloc-tls, alloc-fmt, object-alloc, mmap-alloc

  • License Apache-2.0/MIT is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• google

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

• spore

  • Crate is 'reserved'

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

• boringssl-sys

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

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