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.

• warpack-cli

  • Failed to verify create's content against its repository

    Verified 1 out of 5 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: The crates.io package has no information about its path inside its repository.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: There is no matching git tag containing version '0.0.1'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Number of [[bin]] inconsistent; published=2; orig=0; ed=Set(E2018).

    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.
    • src/bin/
      • util.rs not found.
      • warpack.rs not found.

    Fetched https://github.com/rhazarian/warpack.git 1976a88d58562aca6b6eb9c1a7ff922820dd64db.

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • 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

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/rhazarian/warpack\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency rlua 0.16.3 has issues

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

    rlua crate

  • Dependency ron 0.5.1 is significantly outdated

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

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

    ron versions

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

  • 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 bincode 1.2.1 is slightly outdated

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

    bincode versions

  • Dependency clap 2.33.0 is outdated

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

    clap versions

• warpack-stock-data

  • Failed to verify create's content against its repository

    Verified 1 out of 88 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: The crates.io package has no information about its path inside its repository.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: There is no matching git tag containing version '0.0.1'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • build.rs not found.
    • Cargo.toml.orig does not match the repository.
    • data/doodads/
      • doodadskins.txt not found.
      • doodadmetadata.slk not found.
      • doodads.slk not found.
    • lightningdata.slk not found.
    • terrain.slk not found.
    • data/ui/
      • worldeditlayout.txt not found.
      • worldeditlicense.en.txt not found.
      • aieditordata.txt not found.
      • miscdata.txt not found.
      • triggerdata.txt not found.
      • skinmetadata.slk not found.
      • worldeditdata.txt not found.
      • uniteditordata.txt not found.
    • data/units/
      • neutralunitfunc.txt not found.
      • abilitybuffdata.slk not found.
      • upgradeeffectmetadata.slk not found.
      • unitabilities.slk not found.
      • campaignupgradefunc.txt not found.
      • destructabledata.slk not found.
      • orcabilityfunc.txt not found.
      • campaignabilityfunc.txt not found.
      • commonabilityfunc.txt not found.
      • destructablemetadata.slk not found.
      • miscmetadata.slk not found.
      • unitskin.txt not found.
      • itemskin.txt not found.
      • humanunitfunc.txt not found.
      • miscgame.txt not found.
      • unitbalance.slk not found.
      • unitdata.slk not found.
      • unitmetadata.slk not found.
      • neutralabilityfunc.txt not found.
      • unitui.slk not found.
    • data/units_en/
      • itemstrings.txt not found.
      • nightelfabilitystrings.txt not found.
      • nightelfunitstrings.txt not found.
      • campaignupgradestrings.txt not found.
      • orcunitstrings.txt not found.
      • undeadabilitystrings.txt not found.
      • undeadupgradestrings.txt not found.
      • campaignabilitystrings.txt not found.
      • orcabilitystrings.txt not found.
      • nightelfupgradestrings.txt not found.
      • commonabilitystrings.txt not found.
      • neutralupgradestrings.txt not found.
      • campaignunitstrings.txt not found.
      • orcupgradestrings.txt not found.
      • commandstrings.txt not found.
      • humanabilitystrings.txt not found.
      • humanupgradestrings.txt not found.
      • humanunitstrings.txt not found.
      • undeadunitstrings.txt not found.
      • unitglobalstrings.txt not found.
    • lib.rs not found.

    Fetched https://github.com/rhazarian/warpack.git 1976a88d58562aca6b6eb9c1a7ff922820dd64db.

    Checked on 2024-07-24

    Forum thread

  • Missing categories

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

    List of available categories

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/rhazarian/warpack\.git

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

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

    More info

  • Dependency bincode 1.2.1 is slightly outdated

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

    bincode versions

• warpack-lua-parser

  • Missing categories

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

    List of available categories

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/rhazarian/warpack\.git

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

• warpack-formats

  • Failed to verify create's content against its repository

    Verified 1 out of 11 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: The crates.io package has no information about its path inside its repository.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • warning: There is no matching git tag containing version '0.0.1'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • Cargo.toml.orig does not match the repository.
    • src/
      • lib.rs not found.
      • object.rs not found.
      • metadata.rs not found.
      • objectstore.rs not found.
      • error.rs not found.
    • src/parser/
      • w3obj.rs not found.
      • crlf.rs not found.
      • profile.rs not found.
      • slk.rs not found.

    Fetched https://github.com/rhazarian/warpack.git 1976a88d58562aca6b6eb9c1a7ff922820dd64db.

    Checked on 2024-07-24

    Forum thread

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/rhazarian/warpack\.git

  • Dependency atoi 0.3.2 is significantly outdated

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

    atoi versions

  • Dependency byte-slice-cast 0.3.5 is significantly outdated

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

    byte-slice-cast versions

  • Dependency rlua 0.16.3 has issues

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

    rlua crate

  • Dependency slotmap 0.4.0 is significantly outdated

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

    slotmap versions

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

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

    More info

  • Dependency bitflags 1.2.1 is outdated

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

    bitflags versions

  • Dependency indexmap 1.3.2 is outdated

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

    indexmap versions

  • Dependency thiserror 1.0.11 is a bit outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

• warpack-core

  • Missing categories

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

    List of available categories

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/rhazarian/warpack\.git

  • Dependency atoi 0.3.2 is significantly outdated

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

    atoi versions

  • Dependency itertools 0.8.2 is significantly outdated

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

    itertools versions

  • Dependency path-absolutize 1.1.7 is significantly outdated

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

    path-absolutize versions

  • Dependency rlua 0.16.3 has issues

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

    rlua crate

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

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

    More info

  • Dependency indexmap 1.3.2 is outdated

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

    indexmap versions

  • Dependency notify 4.0.15 is outdated

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

    notify versions

  • Dependency thiserror 1.0.11 is a bit outdated

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

    thiserror versions

  • Dependency toml 0.5.6 is outdated

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

    toml versions

  • Failed to verify create's content against its repository

    Verified 12 out of 18 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: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.0.1'.
    • 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.orig does not match the repository.
    • compiler.rs does not match the repository.
    • src/lua/
      • compiler.rs does not match the repository.
      • object.rs does not match the repository.
      • fs.rs does not match the repository.
    • buildscript_lib.lua does not match the repository.

    Looked for the crate in core/. Fetched https://github.com/rhazarian/warpack.git 1976a88d58562aca6b6eb9c1a7ff922820dd64db.

    Checked on 2024-08-04

    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.