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.

• vob

  • Missing keywords

    Help users find your crates. Add keywords = ["bit-vector", "bit-vec", "vector-of-bits", "vec-bool", "backing"] (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.

• vob, lrtable, packedvec, lrpar, lrlex, cfgrammar

  • Dependency bincode 2.0 is significantly outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    bincode versions

• lrpar

  • Dependency unicode-width 0.1.11 is outdated

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

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

    unicode-width versions

  • Dependency vergen 8 is outdated

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

    vergen versions

  • Imprecise dependency requirement indexmap = 2

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

    indexmap versions

• vob, nimbleparse, lrtable, packedvec, lrpar, lang_tester, lrlex, cfgrammar, cactus, fm, rerun_except

  • License Apache-2.0/MIT is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• lang_tester

  • Imprecise dependency requirement termcolor = 1

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

    termcolor versions

  • Missing keywords

    Help users find your crates. Add keywords = ["test-framework", "vm", "compiler", "language-testing", "tester"] (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.

• lrlex

  • Dependency vergen 8 is outdated

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

    vergen versions

  • Missing keywords

    Help users find your crates. Add keywords = ["lexer", "lexer-generator", "parser-generator", "grammar-parser", "lexemes"] (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.

• nimbleparse

  • Missing keywords

    Help users find your crates. Add keywords = ["parser-generator", "grammar", "debugging", "lexer", "error-recovery"] (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.

• lrtable

  • Missing keywords

    Help users find your crates. Add keywords = ["grammar-table", "parser-generator", "lr-parser", "state", "lr-parser-generator"] (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.

• packedvec

  • Missing keywords

    Help users find your crates. Add keywords = ["store", "integer", "element", "integer-vector", "vec"] (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.

• cfgrammar

  • Imprecise dependency requirement indexmap = 2

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

    indexmap versions

• cactus

  • Missing keywords

    Help users find your crates. Add keywords = ["immutability", "pointers", "parent-node", "stack", "tree"] (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.

• fm

  • Missing keywords

    Help users find your crates. Add keywords = ["text-matching", "pattern-matching", "matcher", "multi-line", "fuzzy-matching"] (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.

• rerun_except

  • Latest stable release is old

    It's been over 4 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 keywords

    Help users find your crates. Add keywords = ["cargo-build", "re-run", "rebuild", "gitignore", "globs"] (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.

• snare

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

No issues found in: depub

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