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.

• lib-ruby-parser

  • Dependency pprof 0.12 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.

    pprof versions

  • Failed to verify create's content against its repository

    Verified 75 out of 79 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.
    • parse.rs not found.
    • list.rs not found.
    • gen.rs not found.
    • gen.rs not found.

    Fetched https://github.com/lib-ruby-parser/lib-ruby-parser.git tagged v4.0.6 (acdd6ed1c7190f83928c838884aae4cde5ebee04).

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Imprecise dependency requirement onig = 6

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

    onig versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["parser-implementations"] 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

  • Missing keywords

    Help users find your crates. Add keywords = ["parser", "ruby", "lib-ruby-parser", "testing", "regex"] (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.

• lib-ruby-parser-nodes

  • Locked dependency version liquid = 0.26

    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.

    liquid versions

  • Locked dependency version liquid-core = 0.26

    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.

    liquid-core versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["node", "lib", "ruby", "message", "repo"] (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.

• lib-ruby-parser-ast

  • Failed to verify create's content against its repository

    Verified 17 out of 148 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: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
    • warning: There is no matching git tag containing version '0.55.0'.
    • 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.
    • message_enum.rs not found.
    • gen.rs not found.
    • node_enum.rs not found.
    • src/nodes/types/
      • encoding.rs not found.
      • pin.rs not found.
      • back_ref.rs not found.
      • args.rs not found.
      • reg_opt.rs not found.
      • nth_ref.rs not found.
      • match_alt.rs not found.
      • next.rs not found.
      • array_pattern.rs not found.
      • array.rs not found.
      • hash.rs not found.
      • x_heredoc.rs not found.
      • block_pass.rs not found.
      • defs.rs not found.
      • casgn.rs not found.
      • super_.rs not found.
      • and_asgn.rs not found.
      • gvasgn.rs not found.
      • send.rs not found.
      • dstr.rs not found.
    • finder_gen.rs not found.
    • visit_gen.rs not found.

    Fetched https://github.com/lib-ruby-parser/ast.git 96f4ea63a4be0e09f1693ea93fd4e6672d56dd67.

    Checked on 2024-04-23

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/lib\-ruby\-parser/ast\.git and could not find a README file there.

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

  • Dependency lib-ruby-parser-nodes 0.55.0 is outdated

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

    lib-ruby-parser-nodes versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["node", "operator", "ast", "lib-ruby-parser"] (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.

• unsplash-wallpaper, alloc-from-pool, dependency-tree-svg

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

• lib-ruby-parser, dependency-tree-svg, lib-ruby-parser-ast

  • 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-tree-svg

  • Missing categories

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

    List of available categories

  • Imprecise dependency requirement serde = 1

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

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    serde versions

  • Missing keywords

    Help users find your crates. Add keywords = ["svg", "run", "dependency-tree-svg", "graph", "package-name1"] (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.

• unsplash-wallpaper

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["unsplash-wallpaper", "unsplash", "parallel", "config"] (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.

• lib-ruby-parser-bindings

  • Missing categories

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

    List of available categories

  • Latest stable release is old

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["lib-ruby-parser", "lib-ruby-parser-bindings", "parser"] (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.

• alloc-from-pool

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["pool", "alloc", "allocation", "struct"] (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.

• rust-bison-skeleton

  • Missing categories

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

    List of available categories

• tagged-pointer-as-enum

  • Dependency criterion 0.3 is outdated

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

    criterion versions

  • Latest stable release is old

    It's been over 3 years. 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

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["enums", "tagged-pointers", "pointers", "tagged-enum", "tags"] (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 some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
status = "deprecated" to their Cargo.toml.