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.

• localsetup

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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["filesystem", "network-programming"] 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 = ["local-computer", "automatic", "setup", "user", "repository"] (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.

• medal

  • Dependency iron 0.5.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.

    iron crate

  • Dependency router 0.5 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.

    router crate

  • Dependency structopt 0.2.18 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 bcrypt 0.10 is significantly outdated

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

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

    bcrypt versions

  • Dependency postgres 0.15 is significantly outdated

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

    postgres versions

  • Dependency rand 0.5.5 is significantly outdated

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

    rand versions

  • Dependency reqwest 0.9.19 is significantly outdated

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

    reqwest versions

  • Dependency rusqlite 0.14.0 is significantly outdated

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

    rusqlite versions

  • Dependency serde_yaml 0.8.9 has issues

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

    serde_yaml crate

  • Dependency sha2 0.7 is significantly outdated

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

    sha2 versions

  • Dependency time 0.1.40 is significantly outdated

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

    time versions

  • Dependency webbrowser 0.5.1 is significantly outdated

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

    webbrowser versions

  • Dependency handlebars-iron 0.25.1 is outdated

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

    handlebars-iron versions

  • Dependency mount 0.3 is outdated

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

    mount versions

  • Dependency params 0.7 is outdated

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

    params versions

  • Dependency persistent 0.3 is outdated

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

    persistent versions

  • Dependency staticfile 0.4 is outdated

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

    staticfile versions

  • Dependency urlencoded 0.5 is outdated

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

    urlencoded versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["games", "web-programming::http-server"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["computer-science", "contest", "platform", "database", "migration"] (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.

  • Optional dependency 'postgres' exposed as an implicit feature

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

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.70, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• dementia

  • Latest stable release is old

    It's been over 6 years. How did the experiment go? 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

  • Dependency rand 0.7 is significantly outdated

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

    rand versions

  • Dependency reqwest 0.9 is significantly outdated

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

    reqwest versions

  • Dependency url 1.7 is significantly outdated

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

    url 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

  • License Apache-2.0/GPL-3.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.46, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• glwindow

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in glwindow/. Fetched https://github.com/zgtm/glwindow.git c2c74c1e75f0d8b1daa61da686c02ca922207f5a.

    Checked on 2025-01-19

    This check is experimental.

    Forum thread

  • README missing from the repository

    We've searched https://github\.com/zgtm/glwindow\.git and could not find a README file there.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Dependency png 0.17.6 is outdated

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

    png versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rendering::graphics-api"] to the Cargo.toml.

    List of available categories

  • Missing keywords

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

  • Optional dependency 'png' 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 'png' may have been unintentional.

    Crate features

• lcd1602rs

  • README missing from the repository

    We've searched https://git\.zgtm\.de/zgtm/lcd1602rs and could not find a README file there.

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["raspberry-pi", "lcd1602", "write", "i2c"] (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.

• kasimir, kasi, kasimir-sys

  • Missing categories

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

    List of available categories

• kasimir, kasi, kasimir-sys

  • README missing from the repository

    We've searched https://git\.zgtm\.de/zgtm/kasimir and could not find a README file there.

• kasi

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in kasi/. Fetched https://git.zgtm.de/zgtm/kasimir 36d79d3725be0812e9ba9853d4a5a91a5192010f.

    Checked on 2024-12-08

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["wifi", "command-line-tool", "devices", "hs100", "plugs-and-devices"] (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.

• kasimir-sys

  • Published crate doesn't match its repository

    Partially verified 4 files (includes 2 Cargo-generated).

    Looked for the crate in kasimir-sys/. Fetched https://git.zgtm.de/zgtm/kasimir 0db5b00f81a7999ea8e798a4b2f2ec21b9fb83bb.

    Checked on 2024-12-15

    Forum thread

  • Missing keywords

    Help users find your crates. Add keywords = ["hs100", "wifi", "smart-plugs", "devices", "plugs-and-devices"] (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.

• lcd1602rs, kasimir, kasi, kasimir-sys, cifuzz, cargo-cifuzz, cifuzz-rs, tipp

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

• kasimir

  • Missing keywords

    Help users find your crates. Add keywords = ["devices", "smart-plugs", "wifi", "communication-with-hs100", "plugs-and-devices"] (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.

• cifuzz, cargo-cifuzz, cifuzz-rs

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• tipp

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