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.

• avr-context, range-lock, avr-int24, letmein-proto, avr-stack, movavg, timeslice, letmein-systemd, letmein-seccomp, disktest-rawio, avr-atomic, shr3

  • 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

• avr-context

  • Failed to verify create's content against its repository

    Verified 7 out of 8 files (includes 1 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.

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

    • README.html not found.

    Fetched https://github.com/mbuesch/avr-context.git tagged avr-context-2.0.1 (eb1dbe39ff4870fd1af7be5a38cf2f6a6c456413).

    Checked on 2026-03-15

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement critical-section = 1

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

    critical-section versions

• disktest-rawio

  • Failed to verify create's content against its repository

    Verified 7 out of 8 files (includes 2 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.

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

    • Cargo.lock not found.
    • README.html not found.

    Looked for the crate in disktest-rawio/. Fetched https://github.com/mbuesch/disktest.git tagged disktest-rawio-2.1.0 (0440f746a99f5c0baa6bb39d9d4e2bb6dc147856).

    Checked on 2026-04-26

    Forum thread

• letmein-proto, letmein-systemd, letmein-seccomp, disktest-rawio

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

• timeslice

  • Dependency esp-idf-hal 0.44 is outdated

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

    esp-idf-hal versions

  • Dependency esp-idf-svc 0.49 is outdated

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

    esp-idf-svc versions

  • Failed to verify create's content against its repository

    Verified 23 out of 24 files (includes 1 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.
    • warning: The crates.io package has no information about its path inside its repository.

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

    • README.html not found.

    Fetched https://github.com/mbuesch/timeslicers.git tagged timeslice-0.5.0 (4b5b0cf912ae5e70f414f81d6a3aad1ee12b81f2).

    Checked on 2025-04-27

    Forum thread

• avr-int24

  • Failed to verify create's content against its repository

    Verified 12 out of 13 files (includes 1 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.

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

    • README.html not found.

    Looked for the crate in avr-int24/. Fetched https://github.com/mbuesch/avr-int24.git tagged avr-int24-1.1.0 (a1a0003d470b957a91b4dc476b12c36860b10e04).

    Checked on 2025-10-31

    Forum thread

• avr-stack

  • Failed to verify create's content against its repository

    Verified 7 out of 8 files (includes 1 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.
    • warning: The crates.io package has no information about its path inside its repository.

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

    • README.html not found.

    Fetched https://github.com/mbuesch/avr-stack.git tagged avr-stack-1.0.0 (73635c0d4a0ff0a37a7f50166906021927ac69a2).

    Checked on 2026-03-15

    Forum thread

• peekable-fwd-bwd

  • 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

  • Failed to verify create's content against its repository

    Verified 6 out of 7 files (includes 1 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.

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

    • README.html not found.

    Fetched https://github.com/mbuesch/peekable-fwd-bwd.git tagged peekable-fwd-bwd-1.0.0 (bffebda252a1bc98752a9c9bb3165da75d7d0632).

    Checked on 2024-07-28

    Forum thread

• movavg

  • Imprecise dependency requirement autocfg = 1

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

    autocfg versions

• curveipo

  • 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

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

    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

• shr3

  • Imprecise dependency requirement autocfg = 1

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

    autocfg 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

• avr-atomic

  • Failed to verify create's content against its repository

    Verified 7 out of 8 files (includes 1 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.

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

    • README.html not found.

    Fetched https://github.com/mbuesch/avr-atomic.git tagged avr-atomic-1.0.0 (a23ce78ef80cc3bffe09650859c991da07964f80).

    Checked on 2025-11-23

    Forum thread

• letmeind

  • Internal error

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

• letmeinfwd

  • Internal error

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

• letmein

  • Internal error

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

• letmein-fwproto

  • Internal error

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

• letmein-conf

  • Internal error

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

• disktest

  • Internal error

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

• disktest-lib

  • Internal error

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

• periodic-audit

  • Internal error

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

• avr-q

  • Internal error

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

• adxl345_driver2

  • Internal error

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