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.

• bootspec

  • Dependency thiserror 1.0.40 is outdated

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

    thiserror versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["encoding"] 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 = ["nixos", "datatype", "rfc", "struct", "specification"] (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.

• detsys-ids-client

  • 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 sysinfo 0.36.0 is significantly outdated

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

    sysinfo versions

  • Dependency reqwest 0.12.12 is outdated

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

    reqwest versions

  • Imprecise dependency requirement tokio = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as tokio = "1.49.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 = ["network-programming"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["events", "http-transport", "system", "determinate", "client"] (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.

• nix-installer

  • Dependency which 6.0.0 is significantly outdated

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

    which versions

  • Dependency dirs 5.0.0 is outdated

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

    dirs versions

  • Dependency nix 0.29.0 is outdated

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

    nix versions

  • Dependency rand 0.8.5 is outdated

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

    rand versions

  • Dependency reqwest 0.12.4 is outdated

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

    reqwest versions

  • Dependency strum 0.26.1 is outdated

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

    strum versions

  • Dependency sysctl 0.5.4 is outdated

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

    sysctl versions

  • Dependency target-lexicon 0.12.4 is outdated

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

    target-lexicon versions

  • Dependency thiserror 1.0.61 is outdated

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

    thiserror versions

  • Imprecise dependency requirement clap = 4

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

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["nix-build", "macos", "install", "nix-flakes", "linux"] (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 'color-eyre' 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 'color-eyre', 'is_ci', 'tracing-error', 'clap', 'eyre', 'tracing-subscriber' may have been unintentional.

    Crate features

• nix-config-parser

  • Dependency thiserror 1.0.38 is outdated

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

    thiserror versions

  • Imprecise dependency requirement indexmap = 2

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

    indexmap versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["config-parser", "nix", "nixos", "file-format", "github"] (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.

• nix-cpio-generator

  • README missing from the repository

    We've searched https://github\.com/determinatesystems/nix\-cpio\-generator\.git and could not find a README file there.

  • Dependency lru 0.8.0 is significantly outdated

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

    lru versions

  • Dependency tokio-util 0.6.7 is significantly outdated

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

    tokio-util versions

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

  • 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

  • Dependency cpio 0.2.2 is outdated

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

    cpio versions

  • Dependency thiserror 1.0.0 is outdated

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

    thiserror versions

  • Dependency zstd 0.11 is outdated

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

    zstd versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["cpio", "closures", "nix", "dump"] (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.

• github-actions-oidc-claims, nix-cpio-generator, cpiotools

  • Missing categories

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

    List of available categories

• cpiotools

  • Dependency base64 0.13.0 is significantly outdated

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

    base64 versions

  • Dependency cpio 0.2.1 is outdated

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

    cpio versions

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["cpio", "hash", "examining", "compare", "structures"] (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.

• github-actions-oidc-claims

  • Missing keywords

    Help users find your crates. Add keywords = ["github-actions", "action", "claim", "run"] (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 issues found in: detsys-srv

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