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.

• hoop, cavity, libwhisper

  • Latest stable release is old

    It's been over 8 years. How did the experiment go? 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

• hoop, cavity, libwhisper, blunder, fft4r

  • 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

• cavity

  • Missing keywords

    Help users find your crates. Add keywords = ["macos", "mkfile", "byte", "fill", "padded"] (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.

• libwhisper

  • Dependency sodiumoxide 0.0.15 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    sodiumoxide crate

  • Dependency bytes 0.4 is significantly outdated

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

    bytes versions

  • Dependency nom 3.2.1 is significantly outdated

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

    nom versions

  • Dependency quick-error 1.2 is outdated

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

    quick-error versions

• blunder

  • 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

  • README missing from the repository

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

  • Dependency errno 0.2 is significantly outdated

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

    errno versions

  • 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

  • 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

• aide-de-camp

  • Dependency bincode 2.0.0-rc.1 is significantly outdated

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

    bincode versions

  • Dependency rand 0.8.5 is outdated

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

    rand versions

  • Dependency thiserror 1.0.30 is outdated

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

    thiserror versions

  • Imprecise dependency requirement tokio = 1

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

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

    List of available categories

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

    Crate features

• uclicious-libucl-sys

  • README missing from the repository

    We've searched https://github\.com/andoriyu/uclicious\-libucl\-sys\.git and could not find a README file there.

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "uclicious-libucl" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

  • Dependency bitflags 1.2 is outdated

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

    bitflags versions

  • 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 = ["ucl", "low-level", "ffi"] (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.

  • Published crate contains binary files

    The crate contains binary files (obscure autoconf code). 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

• baked-spa

  • Dependency axum 0.6 is significantly outdated

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

    axum versions

  • Dependency base64 0.20.0 is significantly outdated

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

    base64 versions

  • Dependency rust-embed 6.4.1 is significantly outdated

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

    rust-embed versions

  • Missing categories

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

    List of available categories

• kissfft-sys

  • Missing categories

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

    List of available categories

  • 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 num-complex 0.3 is significantly outdated

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

    num-complex versions

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "kissfft" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

  • 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

  • Missing keywords

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

• bk_primitives

  • Missing categories

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

    List of available categories

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

    Maintenance status field docs

  • Missing keywords

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

• baked-spa, bk_allocator, bk_primitives, fft4r

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

• uclicious-libucl-sys, blunder, bk_allocator, bk_primitives, fft4r

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

• libnv-sys

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["external-ffi-bindings"] in your Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["freebsd", "bindings", "shouldn-t", "dragon"] (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.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• aide-de-camp, uclicious-libucl-sys, baked-spa

  • 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

• cavity-cli

  • Dependency clap 2 is significantly outdated

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

    clap versions

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

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

    Maintenance status field docs

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Imprecise dependency requirement clap = 2

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

    clap versions

  • Missing keywords

    Help users find your crates. Add keywords = ["macos", "mkfile", "cli", "padded", "zero"] (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.

• uclicious_derive

  • 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 darling 0.10.2 is significantly outdated

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

    darling versions

  • Dependency syn 1.0.16 is significantly outdated

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

    syn 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

• bk_allocator

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

    Maintenance status field docs

  • 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 = ["allocator", "kernel-allocator", "freebsd"] (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.

• fft4r

  • Dependency num-complex 0.3 is significantly outdated

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

    num-complex versions

  • 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

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• cavity-cli, kissfft-sys, uclicious_derive

  • 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

• cavity-cli, kissfft-sys, uclicious_derive, jailet, jaillette

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

• jailet

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• jaillette

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• libnv

  • Internal error

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

• libzetta

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/libzetta ). Please try again later.

• uclicious

  • Internal error

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

• libzetta-zfs-core-sys

  • Internal error

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

• aide-de-camp-sqlite

  • Internal error

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

• cargo-suity

  • Internal error

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

• libzfs_core-sys

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/libzfs_core-sys ) 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.