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.

• mademoiselle_entropia

  • Locked dependency version rug =1.28.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    rug versions

  • Locked dependency version termios =0.3.3

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    termios versions

  • 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

  • Optional dependency 'rug' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'rug' may have been unintentional.

    Crate features

• min_err_per_step

  • Could not find the crate in the repository

    Make sure the main branch of https://github\.com/sark0y/tam\_rusty contains the Cargo.toml for the crate. If you have forked the crate, change the repository property in Cargo.toml to your fork's URL.

  • Locked dependency version rug =1.28.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    rug versions

  • Missing keywords

    Help users find your crates. Add keywords = ["per-step", "min-err", "error", "math", "heart"] (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.

• if

  • Failed to verify create's content against its repository

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

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit 57c06564fffb5457e6f4e0676c5c1e9a4c40e6ea, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • 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.53'.
    • 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=0; orig=1; ed=Set(E2021).

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

    • Cargo.lock not found.
    • Cargo.toml exists, but elsewhere in the repo.
    • Cargo.toml_bkp exists, but elsewhere in the repo.
    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • build.rs exists, but elsewhere in the repo.
    • Cargo.toml.orig does not match the repository.
    • src/
      • lib.rs exists, but elsewhere in the repo.
      • banu.rs exists, but elsewhere in the repo.

    Fetched https://github.com/sark0y/tam_rusty.git 253a2eae1bdb64a2222026781c4ed9010026f445.

    Checked on 2025-11-04

    This check is experimental.

    Forum thread

  • Dependency nix 0.28.0 is significantly outdated

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

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

    nix versions

  • Dependency min_err_per_step 0.0.179 is outdated

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

    min_err_per_step versions

  • Missing keywords

    Help users find your crates. Add keywords = ["numerical", "natural-numbers", "experiment", "trick", "factorize"] (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.

• cups

  • Failed to verify create's content against its repository

    Verified 2 out of 13 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit 57c06564fffb5457e6f4e0676c5c1e9a4c40e6ea, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • 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.5'.
    • 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=0; orig=1; ed=Set(E2021).

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

    • Cargo.lock not found.
    • build.rs exists, but elsewhere in the repo.
    • Cargo.toml_bkp exists, but elsewhere in the repo.
    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • src/
      • lib.rs exists, but elsewhere in the repo.
      • enums.rs does not match the repository.
      • atomic.rs exists, but elsewhere in the repo.
      • some.extra.funx.rs exists, but elsewhere in the repo.
      • stop.flood.rs exists, but elsewhere in the repo.

    Fetched https://github.com/sark0y/tam_rusty.git 253a2eae1bdb64a2222026781c4ed9010026f445.

    Checked on 2025-10-26

    Forum thread

  • Dependency nix 0.28.0 is significantly outdated

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

    nix versions

  • Missing keywords

    Help users find your crates. Add keywords = ["heart", "dev", "pointers", "lib", "kiss"] (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.

• for_build_rs

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in ext/for_build_rs/. Fetched https://github.com/sark0y/tam_rusty.git f3a0ce48b563698001116bb7399f9abbe7a9716f.

    Checked on 2025-08-03

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["lexer", "trick", "lexer-for-build", "console", "file-manager"] (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.

• rst_lex

  • Failed to verify create's content against its repository

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

    • 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.111'.
      • git tag v0.0.111 4ee276448b3c9c840a138aeff70b7319ac9a3039; git push origin --tags

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

    • Cargo.lock not found.

    Looked for the crate in ext/rst_lex/. Fetched https://github.com/sark0y/tam_rusty.git 4ee276448b3c9c840a138aeff70b7319ac9a3039.

    Checked on 2025-09-14

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["console", "lexer", "trick", "github", "file-manager"] (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.

• goto1717

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Optional dependency 'rst_lex' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'rst_lex' may have been unintentional.

    Crate features

• malware_rhapsody

  • Dependency dirs 5.0.1 is outdated

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

    dirs versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'research', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

• sark0y_tam_rst

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/sark0y_tam_rst ) failed. Please try again later.

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