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.

• reductor

  • Published crate doesn't match its repository

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

    Fetched https://github.com/yotamofek/reductor.git c6f5a2d91eff099c19f0cf9054ced40a1f96ca04.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rust-patterns"] 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 = ["reductor", "max", "mean"] (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.

• serde_newtype

  • README missing from the repository

    We've searched https://github\.com/yotamofek/serde\_newtype\.git and could not find a README file there.

  • 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

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Missing categories

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

    List of available categories

  • Missing keywords

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

• packed-vec

  • Latest prerelease 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

  • Published crate doesn't match its repository

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

    Fetched https://github.com/yotamofek/packed-vec.git c31c71ffbf2cda025ad1966f0931fbfdeeb6c55a.

    Checked on 2024-07-28

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/yotamofek/packed\-vec\.git and could not find a README file there.

  • Missing keywords

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

• small-sorted-map

  • Failed to verify create's content against its repository

    Verified 3 out of 11 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not find Cargo.toml for this package in its repo (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: Could not discover crate's location in its repository (via tags).

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

    • Cargo.toml.orig does not match the repository.
    • lib.rs does not match the repository.
    • src/counter/
      • mod.rs not found.
      • serde.rs not found.
    • src/map/
      • mod.rs not found.
      • serde.rs not found.
      • iter.rs not found.
      • entry.rs not found.

    Fetched https://github.com/yotamofek/packed-vec.git 4568ec549ac366643a5480a45d33bc4561bec519.

    Checked on 2024-07-24

    Forum thread

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

    Maintenance status field docs

  • README missing from the repository

    We've searched https://github\.com/yotamofek/packed\-vec\.git and could not find a README file there.

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["map", "sorting", "small-sorted-map"] (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.

• nonzero-const-param

  • Latest prerelease is old

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

  • Published crate doesn't match its repository

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

    Fetched https://github.com/yotamofek/nonzero-const-param.git 0fd04d4ef3e46f46154fb28a95d6c46b1e5f2eb0.

    Checked on 2024-08-10

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/yotamofek/nonzero\-const\-param\.git and could not find a README file there.

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Dependency zerocopy 0.7 is outdated

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

    zerocopy versions

  • Missing keywords

    Help users find your crates. Add keywords = ["nonzero-const-param", "consts", "non-zero"] (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.

• tokio-etcd-lock

  • Imprecise dependency requirement thiserror = 2

    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

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Missing keywords

    Help users find your crates. Add keywords = ["tokio-etcd-lock", "locking", "etcd"] (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.

• tokio-etcd-lock, prefix-varint, ipv4-display

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

• tokio-etcd-lock, packed-vec, prefix-varint, ipv4-display, nonzero-const-param

  • Missing categories

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

    List of available categories

• audio-time

  • 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

  • README missing from the repository

    We've searched https://github\.com/yotamofek/audio\-time\.git and could not find a README file there.

  • 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

  • Published crate doesn't match its repository

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

    Fetched https://github.com/yotamofek/audio-time.git 8f89b1f6edc21b4316cecf78f5e37e4935281294.

    Checked on 2024-08-10

    Forum thread

  • Dependency derive_more 0.99 is outdated

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

    derive_more versions

  • Dependency thiserror 1 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 = ["multimedia::audio"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["audio", "duration", "audio-time", "hz", "system"] (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.

• prefix-varint

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

    Maintenance status field docs

  • Missing keywords

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

• packed-vec, prefix-varint, small-sorted-map, nonzero-const-param, audio-time

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

• ipv4-display

  • Dependency ufmt 0.1.0 is outdated

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

    ufmt 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 keywords

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