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.

• webdog

  • Dependency html5ever 0.29 is significantly outdated

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

    html5ever versions

  • Dependency kuchikiki 0.8.6-speedreader is significantly outdated

    Upgrade to 0.8.8-speedreader to get all the fixes, and avoid causing duplicate dependencies in projects.

    kuchikiki versions

  • Dependency pulldown-cmark 0.12 is significantly outdated

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

    pulldown-cmark versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["template-engine"] 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 = ["site", "page", "dog", "static-site-generator", "fit"] (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 'warp' 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 'warp', 'percent-encoding', 'futures', 'tokio', 'hotwatch' may have been unintentional.

    Crate features

• pupdate

  • Dependency directories 5 is outdated

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

    directories versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["network-programming", "os"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["local", "system", "remote", "helper", "update"] (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.

• hangar-api

  • Missing categories

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

    List of available categories

  • Dependency constcat 0.5 is significantly outdated

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

    constcat versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api", "hangar", "implemented", "far", "ones"] (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.

• pupdate, webdog, hangar-api

  • Imprecise dependency requirement clap = 4

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

    clap versions

• styles

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