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.

• financ

  • README missing from the repository

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

  • Dependency calamine 0.23 is significantly outdated

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

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

    calamine versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/gzsombor/financ.git 5b90cc00525d11ec5630d639e8d0871dbefa1ad7.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency guid-create 0.3 is a bit outdated

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

    guid-create versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • Missing categories

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

• safetensors-cli

  • Published crate doesn't match its repository

    Partially verified 7 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.

    Fetched https://github.com/gzsombor/safetensors-cli.git 6e6d9f153a392fb390da3a1799f777d9a28080c3.

    Checked on 2024-08-10

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/gzsombor/safetensors\-cli\.git and could not find a README file there.

  • Dependency safetensors 0.3.1 is outdated

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

    safetensors versions

  • Imprecise dependency requirement memmap2 = 0

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

    memmap2 versions

  • Missing categories

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

    List of available categories

• financ, safetensors-cli, teraform

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

• teraform

  • README missing from the repository

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

  • Dependency failure 0.1.1 has issues

    It may not be actively developed any more. Consider changing the dependency.

    failure crate

  • Dependency tera 0.11 is significantly outdated

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

    tera versions

  • Latest stable release is old

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

  • 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 clap 2.31.2 is outdated

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

    clap versions

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

  • Missing categories

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