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.

• quickraw

  • Latest prerelease is old

    It's been over 21 months. 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

  • Dependency phf 0.10 is significantly outdated

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

    phf versions

  • Imprecise dependency requirement anyhow = 1

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

  • Dependency image 0.24 is outdated

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

    image versions

  • Dependency thiserror 1 is a bit outdated

    Consider upgrading to 2.0.12 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.

    thiserror versions

  • Missing categories

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

• quickexif

  • Latest prerelease is old

    It's been over 15 months. 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

  • Dependency erreport 0.2 is significantly outdated

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

    erreport versions

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• quickexif, erreport, glr-parser

  • Missing categories

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

    List of available categories

• onshape-level-gen

  • 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 rand 0.8 is a bit outdated

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

    rand versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["game", "gen", "onshape-level-gen"] (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.

• w3s

  • Cryptocurrency crate

    This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.

    Author of this site is firmly convinced that cryptocurrencies have a net-negative effect on society.

• erreport

  • Missing keywords

    Help users find your crates. Add keywords = ["erreport", "report", "path", "why", "invalid-xxx"] (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.

• fn-util

  • 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 syn 1 is significantly outdated

    Upgrade to 2.0.101 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.101". 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.

    syn versions

• glr-parser

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

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

    Maintenance status field docs

  • Dependency regex 0.1.32 is significantly outdated

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

    regex versions

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["glr", "parser", "glr-parser", "testing"] (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.

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