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.

• randomgen

  • Published crate doesn't match its repository

    Verified 4 out of 6 files (includes 3 Cargo-generated).

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

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

    Fetched https://github.com/mohtashimnawaz/random-gen-crate.git 1a3709c7a5aa9394ca0ee07177b44da34ea67414.

    Checked on 2025-03-21

    This check is experimental.

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/mohtashimnawaz/random\-gen\-crate\.git and could not find a README file there.

  • No readme property

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

• configloader-676

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2025-03-21

    Forum thread

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

• adv_fs_utils

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

    bytesize versions

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