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.

• alevin-fry

  • Dependency noodles 0.85.0 is significantly outdated

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

    noodles versions

  • Dependency bincode 1.3.3 is slightly outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    bincode versions

  • Dependency petgraph 0.6.5 is a bit outdated

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

    petgraph versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency typed-builder 0.20.0 is outdated

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

    typed-builder versions

  • Failed to verify create's content against its repository

    Partially verified 32 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.11.2'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Fetched https://github.com/combine-lab/alevin-fry.git ffc485ec33634a5a49ac6ecf599dd78d26705cdd.

    Checked on 2025-03-15

    This check is experimental.

    Forum thread

• cargiao

  • 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

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

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

  • 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

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

    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 = ["giao", "cargiao", "heading"] (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.

• libradicl

  • Dependency noodles 0.85.0 is significantly outdated

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

    noodles versions

  • Dependency itertools 0.13.0 is outdated

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

    itertools versions

  • Imprecise dependency requirement snap = 1

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

    snap versions

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