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.

• nvml-wrapper

  • Dependency libloading 0.8.1 is a bit outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    libloading versions

  • Dependency thiserror 1.0 is outdated

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

    thiserror versions

• jsonnet-go

  • Published crate doesn't match its repository

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

    Fetched https://github.com/swlynch99/jsonnet-go-rs.git c3e6411a05e21254223537d74b3d404766d229db.

    Checked on 2024-09-22

    This check is experimental.

    Forum thread

  • 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

• metriken-core

  • Failed to verify create's content against its repository

    Verified 1 out of 14 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit 26dbac76306c976cadecb01c7adebc0cbb0708f9, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: There is no matching git tag containing version '0.1.3'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.
    • error: Manifest properties don't match: package.build: crates.io=build.rs, orig=<unset>.
      • If you have a monorepo, you can use git tags in format cratename/v0.1.3

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

    • build.rs exists, but elsewhere in the repo.
    • CHANGELOG.md not found.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • src/
      • lib.rs not found.
      • metadata.rs exists, but elsewhere in the repo.
      • provide.rs not found.
      • metrics.rs not found.
      • formatter.rs exists, but elsewhere in the repo.
      • dynmetrics.rs not found.
      • null.rs exists, but elsewhere in the repo.
      • wrapper.rs not found.

    Fetched https://github.com/pelikan-io/rustcommon.git cf6a085a94a94b98c0084bb59e4df7eac35a5114.

    Checked on 2024-12-15

    Forum thread

  • Dependency phf 0.11 is outdated

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

    phf versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["value-formatting"] 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 = ["metrics", "name", "registered", "declare", "static"] (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.

• jsonnet-go-sys

  • Missing categories

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

    List of available categories

  • Dependency target-lexicon 0.12.12 is outdated

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

    target-lexicon versions

  • Missing keywords

    Help users find your crates. Add keywords = ["jsonnet", "go-jsonnet", "bindings", "error-message", "field"] (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.

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

    Detecting docs.rs

• cargo-deduplicate-warnings

  • Dependency cargo_metadata 0.18.1 is outdated

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

    cargo_metadata versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::cargo-plugins"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["json-output", "deduplicate", "warnings", "cargo", "message"] (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.

No issues found in: substruct

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