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.

• async-tls

  • Dependency rustls ^0.21 is significantly outdated

    Upgrade to the latest version 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.

    rustls versions

  • Dependency rustls-webpki ^0.101.4 is significantly outdated

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

    rustls-webpki versions

  • Dependency webpki-roots ^0.22.3 is significantly outdated

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

    webpki-roots versions

  • Dependency rustls-pemfile ^1.0 is outdated

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

    rustls-pemfile versions

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

    Use OR instead of /.

    SPDX license list

  • Missing keywords

    Help users find your crates. Add keywords = ["tls", "server", "rustls", "client", "async-stream"] (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.

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

    Crate features

• ffi-opaque, db-key, needy, futures-poll-log

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

• db-key

  • Latest stable release is old

    It's been over 11 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 = ["database"] 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 = ["key", "datatype", "database"] (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.

• ffi-opaque

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

    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

• qnxscreen-sys

  • Missing categories

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

    List of available categories

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "qnxscreen" 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.

  • Missing keywords

    Help users find your crates. Add keywords = ["qnx", "low-level", "api", "screen", "build"] (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.

  • 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

• attr, leveldb-rs, futures-poll-log, escapade

  • 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

• leveldb-rs

  • README missing from the repository

    We've searched https://github\.com/andrew\-d/leveldb\-rs\.git and could not find a README file there.

  • Missing categories

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

    List of available categories

• needy

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-11-17

    This check is experimental.

    Forum thread

• db-key, attr, leveldb-rs, futures-poll-log, escapade, crates-io-changes

  • 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

• leveldb-rs, ferrous-systems, ferrocene

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

• escapade

  • Dependency skeptic ^0.6.1 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.

    skeptic crate

  • Missing categories

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

    List of available categories

• futures-poll-log

  • Dependency futures ^0.1 has issues

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

    futures crate

  • Dependency log ^0.3 is significantly outdated

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

    log versions

• crates-io-changes

  • Missing categories

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

    List of available categories

  • Dependency git2 ^0.6 is significantly outdated

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

    git2 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

  • Missing keywords

    Help users find your crates. Add keywords = ["index", "io", "file", "iterate", "file-sorting"] (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.

• attr

  • Missing categories

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

    List of available categories

• cargo-needy

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

• ferrous-systems

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• ferrocene

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• highgear

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• highgear, criticalup, lazers, criticalup-cli

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

• criticalup

  • Crate is 'reserved'

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

• lazers

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• criticalup-cli

  • Crate is 'reserved'

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

• qnxscreen

  • Internal error

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

• async-std

  • Internal error

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

• criticaltrust

  • Internal error

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

• tide

  • Internal error

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

• leveldb-sys

  • Internal error

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

• leveldb

  • Internal error

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

• panic_at_the_disco

  • Internal error

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

• strand

  • Internal error

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

• drossel-journal

  • Internal error

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

• drossel

  • Internal error

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