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.

• bmf-parse

  • Failed to verify create's content against its repository

    Verified 5 out of 10 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 169349cf12153077692692e6a35684a32d806ef3, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • 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.lock does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • simple.rs does not match the repository.
    • src/
      • base.rs does not match the repository.
      • lib.rs does not match the repository.
      • macro.rs does not match the repository.

    Fetched https://github.com/gamingliamstudios/bmf-parse.git 47df8e4173541cc98bf35d6605c08e1433b838f7.

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

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