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.

• veriwasm

  • Dependency elfkit 0.0.4 is significantly outdated

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

    elfkit versions

  • Dependency env_logger 0.8.4 is significantly outdated

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

    env_logger versions

  • Dependency goblin 0.4.1 is significantly outdated

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

    goblin versions

  • Dependency object 0.21.0 is significantly outdated

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

    object versions

  • Dependency petgraph 0.4.13 is significantly outdated

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

    petgraph versions

  • Dependency wasmtime 0.28.0 is significantly outdated

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

    wasmtime versions

  • Dependency clap 2.33.3 is outdated

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

    clap versions

  • Dependency colored 2.0.0 is a bit outdated

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

    colored versions

  • Dependency itertools 0.10.1 is outdated

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

    itertools versions

  • Dependency lucet-module 0.5.1 is significantly outdated

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

    lucet-module versions

  • Dependency yaxpeax-arch 0.2.4 is outdated

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

    yaxpeax-arch versions

  • Dependency yaxpeax-x86 1.0.4 is outdated

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

    yaxpeax-x86 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 categories

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

• equationx

  • Dependency lalrpop 0.20.2 is outdated

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

    lalrpop versions

  • Dependency lalrpop-util 0.20.2 is outdated

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

    lalrpop-util versions

  • Failed to verify create's content against its repository

    Verified 12 out of 13 files (includes 2 Cargo-generated).

    • warning: Crate tarball has been published from the commit f827c6e7c110d35b9512b0f3f31a8146a3ad4987, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

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

    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/schism-pl/equationx.git 5a8753870ffd6a46ef3a26fa268ceed5956f2026.

    Checked on 2025-02-16

    This check is experimental.

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["math", "parser", "expressions", "evaluating", "equations"] (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.

• xyzvec

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["vector", "fixed-size", "fixed-point", "statically", "allocated"] (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.

• extra_args

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency syn 1.0.76 is significantly outdated

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

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