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.

• caps

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

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.63, which is newer than the last 2018-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

• caps, zbus_systemd, libsystemd, lpc81x-pac, lpc13xx-pac, efuse, likemod, appc, modinsert

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

    Use OR instead of /.

    SPDX license list

• prometheus

  • Dependency procfs ^0.17 is outdated

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

    procfs versions

  • Dependency reqwest ^0.12 is outdated

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

    reqwest versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::debugging", "development-tools::profiling"] 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

  • Optional dependency 'reqwest' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'reqwest', 'libc', 'protobuf-codegen', 'procfs' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

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

    The Edition Guide

• zbus_systemd, dkregistry, appc

  • Imprecise dependency requirement serde = 1

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

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    serde versions

• lpc81x-pac

  • Dependency bare-metal 1.0.0 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.

    bare-metal crate

  • 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

• pamsm

  • 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 bitflags 1.0 is outdated

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

    bitflags versions

  • Using outdated edition for no reason

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

• libsystemd

  • Dependency hmac ^0.12 is a bit outdated

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

    hmac versions

  • Dependency nix ^0.29 is outdated

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

    nix versions

  • Dependency sha2 ^0.10 is a bit outdated

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

    sha2 versions

• dkregistry

  • Dependency base64 0.13 is significantly outdated

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

    base64 versions

  • Dependency reqwest 0.10 is significantly outdated

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

    reqwest versions

  • Dependency sha2 ^0.9.0 is significantly outdated

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

    sha2 versions

  • Dependency strum 0.19 is significantly outdated

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

    strum versions

  • Dependency strum_macros 0.19 is significantly outdated

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

    strum_macros versions

  • Dependency tokio 0.2 has issues

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

    tokio crate

  • Dependency http 0.2 is outdated

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

    http versions

  • Dependency libflate 1.0 is outdated

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

    libflate versions

  • Dependency thiserror 1.0.19 is outdated

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

    thiserror 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 = ["network-programming"] to the Cargo.toml.

    List of available categories

• caps, zbus_systemd, likemod, modinsert

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] to the Cargo.toml.

    List of available categories

• appc

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

    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 = ["…"] to the Cargo.toml.

    List of available categories

  • Dependency error-chain 0.10 has issues

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

    error-chain crate

  • Dependency nix 0.8 is significantly outdated

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

    nix versions

  • Dependency semver 0.6 is significantly outdated

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

    semver versions

  • Dependency sha2 0.5 is significantly outdated

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

    sha2 versions

  • Failed to verify create's content against its repository

    Verified 11 out of 12 files (includes 0 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • error: Cargo.toml.orig from the crate tarball could not be verified.

    Fetched https://github.com/camallo/appc-rs.git tagged 0.0.1-dev.4 (8978c6d258498d11c37f26313206afed2191b49a).

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

• lpc13xx-pac

  • Dependency bare-metal 1.0.0 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.

    bare-metal crate

  • 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

• lpc81x-pac, lpc13xx-pac, likemod, appc, modinsert

  • 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

• likemod

  • Dependency errno 0.2 is significantly outdated

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

    errno versions

  • Dependency error-chain 0.12 has issues

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

    error-chain crate

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency tokio 0.1 has issues

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

    tokio crate

  • 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

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

    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

• efuse

  • 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 = ["filesystem"] to the Cargo.toml.

    List of available categories

• modinsert

  • Dependency nix 0.9 is significantly outdated

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

    nix 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

No issues found in: memfd

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