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.

• genawaiter

  • Dependency proc-macro-hack 0.5 has issues

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

    proc-macro-hack crate

• rlbot

  • Dependency flatbuffers 0.5.0 is significantly outdated

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

    flatbuffers versions

  • Dependency libloading 0.5.0 is significantly outdated

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

    libloading versions

  • Dependency nalgebra 0.18.0 is significantly outdated

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

    nalgebra versions

  • Dependency smallvec 0.6.9 is significantly outdated

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

    smallvec versions

  • Dependency ratelimit 0.4.3 is outdated

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

    ratelimit versions

  • Missing categories

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

• war

  • Dependency byteordered 0.4.0 is significantly outdated

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

    byteordered versions

  • Dependency failure 0.1.5 has issues

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

    failure crate

  • Dependency num_enum 0.4.1 is significantly outdated

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

    num_enum versions

  • Dependency scroll 0.9.2 is significantly outdated

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

    scroll versions

  • Buggy README path

    The non-local path to readme specified as \.\./\.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Dependency indexmap 1.2.0 is outdated

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

    indexmap versions

• war-cli

  • Dependency structopt 0.3.1 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Dependency failure 0.1.5 has issues

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

    failure crate

  • Buggy README path

    The non-local path to readme specified as \.\./\.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

  • Dependency notify 4.0.13 is outdated

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

    notify versions

• genawaiter, rlbot, war, war-cli, genawaiter-macro, genawaiter-proc-macro

  • Latest stable release is old

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

• inside-baseball

  • Dependency clap 3.2.19 is significantly outdated

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

    clap 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

  • Dependency indexmap 1.9.1 is outdated

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

    indexmap versions

  • Dependency tracing-tree 0.2.1 is outdated

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

    tracing-tree versions

• ingress-status-sync

  • Dependency k8s-openapi 0.11.0 is significantly outdated

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

    k8s-openapi versions

  • Dependency kube 0.52.0 is significantly outdated

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

    kube versions

  • Dependency kube-runtime 0.52.0 is significantly outdated

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

    kube-runtime versions

  • Dependency tracing-subscriber 0.2.17 is significantly outdated

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

    tracing-subscriber 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").

    Maintenance status field docs

• war, war-cli, genawaiter-macro, chip, genawaiter-proc-macro, cope, winner

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

• chip

  • Dependency nalgebra 0.18.0 is significantly outdated

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

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

    More info

  • Latest stable release is old

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Published crate contains binary files

    The crate contains binary files (static library). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• genawaiter-macro

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

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

    Use OR instead of /.

    SPDX license list

• genawaiter-proc-macro

  • Dependency proc-macro-error 0.4 is significantly outdated

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

    proc-macro-error versions

  • Dependency proc-macro-hack 0.5 has issues

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

    proc-macro-hack crate

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

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

    Use OR instead of /.

    SPDX license list

• cope-dom

  • Missing categories

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

    List of available categories

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

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

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["cope-dom", "dom", "cope", "testing", "firefox"] (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.

• cope

  • Missing categories

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

    List of available categories

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

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

    Maintenance status field docs

  • Missing keywords

    Help users find your crates. Add keywords = ["cope"] (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.

• winner

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• nirvana, codi

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

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