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.

• xterm-js-sys

  • Failed to verify create's content against its repository

    Verified 20 out of 23 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: There is no matching git tag containing version '4.6.0-alpha1'.
    • 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:

    • bindings-left.ts not found.
    • bindings.ts not found.
    • README.md does not match the repository.

    Fetched https://github.com/rrbutani/xterm-js-sys.git 4af06a7c0adad582e9c9338826e76e1c5b6ea16b.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

• lc3tools-sys

  • Dependency bindgen 0.54.0 is significantly outdated

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

    bindgen versions

  • Dependency pretty_assertions 0.6 is significantly outdated

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

    pretty_assertions versions

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

• xterm-js-sys, lc3tools-sys, lc3-isa, lc3-macros

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

    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

• bazel-execlog-cmp

  • Dependency color-eyre 0.5 is significantly outdated

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

    color-eyre versions

  • Dependency indicatif 0.16 is significantly outdated

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

    indicatif versions

  • Dependency rustyline 8.0 is significantly outdated

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

    rustyline versions

  • Dependency serde-aux 2.2 is significantly outdated

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

    serde-aux versions

  • Dependency prettydiff 0.4 is a bit outdated

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

    prettydiff 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

• xterm-js-sys, lc3tools-sys, lc3-isa, lc3-macros, rp-pio

  • 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

• xterm-js-sys, lc3tools-sys, ubench

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

• tower-web-protobuf

  • Dependency bytes 0.4.12 is significantly outdated

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

    bytes versions

  • Dependency futures 0.1.25 has issues

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

    futures crate

  • Dependency http 0.1.14 is significantly outdated

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

    http versions

  • Dependency prost 0.5.0 is significantly outdated

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

    prost versions

  • Dependency prost-build 0.5.0 is significantly outdated

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

    prost-build versions

  • Dependency serde_plain 0.3.0 is significantly outdated

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

    serde_plain versions

  • Dependency tower-service 0.1.0 is significantly outdated

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

    tower-service versions

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["protobuf", "tower-web-protobuf", "json", "protobuf-middleware", "response"] (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.

• ubench

  • Latest prerelease is old

    It's been over 2 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

  • Dependency riscv 0.8 is significantly outdated

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

    riscv versions

  • Dependency embedded-hal 0.2 is a bit outdated

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

    embedded-hal versions

  • Dependency owo-colors 3.4 is a bit outdated

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

    owo-colors versions

  • Dependency unicode-width 0.1 is a bit outdated

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

    unicode-width versions

  • Imprecise dependency requirement nb = 1

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

    nb versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["microcontrollers", "benchmark", "ubench", "micro-controller", "processing"] (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.

• lc3tools-sys, tower-web-protobuf, rp-pio

  • 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

• lc3-isa

  • Dependency arbitrary 0.4.1 is significantly outdated

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

    arbitrary versions

  • Failed to verify create's content against its repository

    Verified 11 out of 12 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.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: There is no matching git tag containing version '0.1.0-alpha0'.
    • 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.

    Looked for the crate in isa/. Fetched https://github.com/ut-utp/prototype.git d6fe45b22d7af2f09dbaeeddcbdfaa3692c5816a.

    Checked on 2024-07-28

    Forum thread

• lc3-macros

  • Failed to verify create's content against its repository

    Verified 4 out of 5 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.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: There is no matching git tag containing version '0.1.0-alpha0'.
    • 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.

    Looked for the crate in macros/. Fetched https://github.com/ut-utp/prototype.git d6fe45b22d7af2f09dbaeeddcbdfaa3692c5816a.

    Checked on 2024-07-28

    Forum thread

  • Dependency syn 1.0.5 is significantly outdated

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

    syn versions

• rp-pio

  • Missing categories

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

    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.

  • Missing keywords

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