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.

• rquickjs

  • Imprecise dependency requirement either = 1

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

    either versions

  • Optional dependency 'indexmap-rs' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'indexmap-rs', 'rquickjs-macro', 'either-rs' may have been unintentional.

    Crate features

• rquickjs-sys

  • *-sys crate without links property

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

  • Dependency bindgen 0.69 is 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

  • Imprecise dependency requirement cc = 1

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

    cc versions

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["web-programming", "external-ffi-bindings"] in your 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

• reblessive, dreck

  • Missing categories

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

    List of available categories

• dreck

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

• rquickjs-core

  • Published crate doesn't match its repository

    Partially verified 75 files (includes 4 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.9.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in core/. Fetched https://github.com/delskayn/rquickjs.git d4a6b2aa3c6bba0448ac54209dfec44f310e276f.

    Checked on 2025-02-02

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement async-lock = 3

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

    async-lock versions

  • Optional dependency 'dlopen' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'dlopen', 'either', 'chrono', 'indexmap', 'relative-path' may have been unintentional.

    Crate features

• rquickjs-macro

  • Published crate doesn't match its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.9.0'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Cargo.toml.orig from crates.io is not an exact match with the repository.

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

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

    Looked for the crate in macro/. Fetched https://github.com/delskayn/rquickjs.git d4a6b2aa3c6bba0448ac54209dfec44f310e276f.

    Checked on 2025-02-16

    Forum thread

  • Dependency convert_case 0.6 is a bit outdated

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

    convert_case versions

  • Imprecise dependency requirement indexmap = 2

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

    indexmap versions

  • Optional dependency 'phf_shared' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'phf_shared', 'phf_generator' may have been unintentional.

    Crate features

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