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.

• bitcasky

  • 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

  • Dependency dashmap 5.5.3 is outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    dashmap versions

  • Dependency fs4 0.6.6 is outdated

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

    fs4 versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency rustix 0 is outdated

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

    rustix versions

  • Failed to verify create's content against its repository

    Verified 28 out of 36 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 '0.1.2'.
    • 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 exists, but elsewhere in the repo.
    • Cargo.toml.orig does not match the repository.
    • mmap_data_storage.rs does not match the repository.
    • src/
      • test_utils.rs does not match the repository.
      • options.rs does not match the repository.
      • clock.rs does not match the repository.
    • file_lock.rs does not match the repository.
    • tests/
      • test_read_write.rs does not match the repository.
      • test_merge.rs does not match the repository.

    Fetched https://github.com/ylgrgyq/bitcasky.git f358a3be7a002b1a728dc1e0acab93217e72b806.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["bitcasky", "store", "database", "value", "io"] (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.

• json0-rs

  • Missing categories

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

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

  • Dependency itertools 0.11.0 is significantly outdated

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

    itertools versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/ylgrgyq/json0-rs.git 93561de72f7d5f9149ef398872101b0158fe6dcd.

    Checked on 2024-07-28

    Forum thread

  • Dependency base64 0.21.0 is outdated

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

    base64 versions

  • Dependency dashmap 5.4.0 is outdated

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

    dashmap versions

  • Dependency thiserror 1.0.38 is a bit outdated

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

    thiserror versions

  • Missing keywords

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

• bitcasky-database

  • Dependency dashmap 5.5.3 is outdated

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

    dashmap versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.1'.
      • git tag v0.1.1 dd9c4e602e675c8385d23d9cbea5b56162807f10; git push origin --tags

    Looked for the crate in lib/bitcasky-database/. Fetched https://github.com/ylgrgyq/bitcask.git dd9c4e602e675c8385d23d9cbea5b56162807f10.

    Checked on 2024-08-10

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["bitcasky", "database", "lib", "io", "value"] (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.

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

• bitcasky-common

  • Dependency fs4 0.6.6 is outdated

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

    fs4 versions

  • Dependency rustix 0 is outdated

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

    rustix versions

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.1.1'.
      • git tag v0.1.1 dd9c4e602e675c8385d23d9cbea5b56162807f10; git push origin --tags

    Looked for the crate in lib/bitcasky-common/. Fetched https://github.com/ylgrgyq/bitcask.git dd9c4e602e675c8385d23d9cbea5b56162807f10.

    Checked on 2024-08-10

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["bitcasky", "lib", "bitcasky-common", "database", "value"] (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.

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

• bitcasky, bitcasky-database, bitcasky-common

  • Dependency thiserror 1.0.53 is a bit outdated

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

    thiserror versions

• bitcasky, bitcasky-database, bitcasky-common

  • Missing categories

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

    List of available categories

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