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.

• osmpbfreader

  • Published crate doesn't match its repository

    Partially verified 22 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Fetched https://github.com/texitoi/osmpbfreader-rs.git 092f91e51d04473df9654116034af925f0069dc5.

    Checked on 2025-06-01

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement protobuf = 3

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

    protobuf versions

  • Imprecise dependency requirement protobuf-codegen = 3

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

    protobuf-codegen versions

• keyberon

  • Dependency arraydeque 0.4.5 is significantly outdated

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

    arraydeque versions

  • Dependency generic-array 0.13 is significantly outdated

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

    generic-array versions

  • Dependency heapless 0.5 is significantly outdated

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

    heapless versions

  • Dependency embedded-hal 0.2 is outdated

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

    embedded-hal versions

  • Dependency usb-device 0.2.0 is outdated

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

    usb-device 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").

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• structopt-derive

  • Dependency heck 0.3.0 is significantly outdated

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

    heck versions

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

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

    syn versions

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

    Use OR instead of /.

    SPDX license list

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

• par-map

  • Dependency futures 0.1.13 has issues

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

    futures crate

  • Dependency futures-cpupool 0.1.5 has issues

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

    futures-cpupool 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

• mdo

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rust-patterns"] 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

• cp_sat

  • Dependency prost 0.8 is significantly outdated

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

    prost versions

  • Dependency prost-build 0.8 is significantly outdated

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

    prost-build versions

• coin_cbc_sys

  • *-sys crate without links property

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

  • 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

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

• mdo, par-map, pub-iterator-type

  • 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

• pub-iterator-type

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

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

    List of available categories

• structopt-derive, cp_sat, structopt

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

    Maintenance status field docs

• structopt

  • Dependency clap 2.33 is outdated

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

    clap versions

No issues found in: coin_cbc

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