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.

• riscv_analysis_cli

  • Failed to verify create's content against its repository

    Verified 5 out of 9 files (includes 2 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.

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • raw.yaml does not match the repository.
    • raw.yaml does not match the repository.
    • Cargo.toml exists, but elsewhere in the repo.
    • raw.yaml exists, but elsewhere in the repo.
    • raw.yaml exists, but elsewhere in the repo.
    • main.rs exists, but elsewhere in the repo.
    • main.rs does not match the repository.

    Looked for the crate in riscv_analysis_cli/. Fetched https://github.com/rajanmaghera/riscv-analysis.git tagged v0.1.0-alpha2 (fb8ccd372ee08fac8c19867253133e62a2ea824e).

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Latest prerelease is old

    It's been over 20 months. 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    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

• riscv_analysis

  • Dependency itertools 0.11.0 is significantly outdated

    Upgrade to 0.14.0 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.

    itertools versions

  • Latest prerelease is old

    It's been over 20 months. 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").

    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.

    More info

  • Dependency getrandom 0.2 is outdated

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

    getrandom versions

  • Dependency lsp-types 0.94.0 is outdated

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

    lsp-types versions

  • Failed to verify create's content against its repository

    Verified 32 out of 48 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.

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

    • Cargo.toml.orig does not match the repository.
    • Cargo.toml exists, but elsewhere in the repo.
    • lib.rs exists, but elsewhere in the repo.
    • riscv_analysis/src/analysis/
      • available.rs exists, but elsewhere in the repo.
      • gen_kill.rs exists, but elsewhere in the repo.
    • riscv_analysis/src/cfg/
      • function.rs exists, but elsewhere in the repo.
      • test_wrapper.rs exists, but elsewhere in the repo.
    • riscv_analysis/src/gen/
      • function_annotations.rs exists, but elsewhere in the repo.
      • directions.rs exists, but elsewhere in the repo.
    • checks.rs exists, but elsewhere in the repo.
    • riscv_analysis/src/parser/
      • parsing.rs exists, but elsewhere in the repo.
      • node.rs exists, but elsewhere in the repo.
      • lexer.rs exists, but elsewhere in the repo.
      • token.rs exists, but elsewhere in the repo.
    • riscv_analysis/src/passes/
      • lint_error.rs exists, but elsewhere in the repo.
      • manager.rs exists, but elsewhere in the repo.
    • mod.rs exists, but elsewhere in the repo.
    • lib.rs does not match the repository.
    • src/analysis/
      • gen_kill.rs does not match the repository.
      • available.rs does not match the repository.
    • src/cfg/
      • test_wrapper.rs does not match the repository.
      • function.rs does not match the repository.
    • src/gen/
      • directions.rs does not match the repository.
      • function_annotations.rs does not match the repository.
    • checks.rs does not match the repository.
    • src/parser/
      • lexer.rs does not match the repository.
      • token.rs does not match the repository.
      • parsing.rs does not match the repository.
      • node.rs does not match the repository.
    • src/passes/
      • lint_error.rs does not match the repository.
      • manager.rs does not match the repository.
    • mod.rs does not match the repository.

    Looked for the crate in riscv_analysis/. Fetched https://github.com/rajanmaghera/riscv-analysis.git tagged v0.1.0-alpha2 (fb8ccd372ee08fac8c19867253133e62a2ea824e).

    Checked on 2024-08-05

    Forum thread

• riscv_analysis_lsp

  • Dependency serde-wasm-bindgen 0.5 is significantly outdated

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

    serde-wasm-bindgen versions

  • Latest prerelease is old

    It's been over 20 months. 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").

    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.

    More info

  • Dependency lsp-types 0.94.0 is outdated

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

    lsp-types versions

  • Failed to verify create's content against its repository

    Verified 5 out of 6 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.

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

    • mod.rs exists, but elsewhere in the repo.
    • mod.rs does not match the repository.

    Looked for the crate in riscv_analysis_lsp/. Fetched https://github.com/rajanmaghera/riscv-analysis.git tagged v0.1.0-alpha2 (fb8ccd372ee08fac8c19867253133e62a2ea824e).

    Checked on 2024-07-28

    Forum thread

  • Imprecise dependency requirement url = 2

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

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