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.

• mlar

  • Failed to verify create's content against its repository

    Verified 7 out of 11 files (includes 2 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.

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

    • create.sh~ not found.
    • Cargo.lock not found.
    • create.sh not found.
    • compare.py not found.
    • compare.py~ not found.

    Looked for the crate in mlar/. Fetched https://github.com/anssi-fr/mla.git tagged mlar-v1.3.0 (ed49793b956c2aef1b52cae4bd742904170ad521).

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

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

    rand versions

  • Dependency rand_chacha 0.3 is outdated

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

    rand_chacha versions

  • Imprecise dependency requirement clap = 4

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

    clap versions

  • Missing keywords

    Help users find your crates. Add keywords = ["mla", "storage", "creation", "format", "use-case"] (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.

• mla

  • Dependency bincode 1.3 is slightly outdated

    Consider upgrading to 2.0.1 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.

    bincode versions

  • Dependency brotli 3.3 is outdated

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

    brotli versions

  • Dependency generic-array 0.14 is slightly outdated

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

    generic-array versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency rand_chacha 0.3 is outdated

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

    rand_chacha versions

  • Imprecise dependency requirement digest = 0

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

    digest versions

  • Missing keywords

    Help users find your crates. Add keywords = ["storage", "layer", "language", "creation", "part"] (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.

• curve25519-parser

  • Dependency der-parser 8 is outdated

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

    der-parser versions

  • Dependency rand_core 0.6 is a bit outdated

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

    rand_core versions

  • Imprecise dependency requirement curve25519-dalek = 4

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

    curve25519-dalek versions

  • Missing keywords

    Help users find your crates. Add keywords = ["key", "layer", "mla", "part", "creation"] (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.

• mla, mlar, curve25519-parser

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["cryptography"] 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 issues found in: git2mail

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