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.

• cnx, cnx-contrib, factori-impl

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

• cnx

  • Dependency async-stream 0.2 is significantly outdated

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

    async-stream versions

  • Dependency cairo-rs 0.8 is significantly outdated

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

    cairo-rs versions

  • Dependency cairo-sys-rs 0.9 is significantly outdated

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

    cairo-sys-rs versions

  • Dependency pango 0.8 is significantly outdated

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

    pango versions

  • Dependency pangocairo 0.9 is significantly outdated

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

    pangocairo versions

  • Dependency xcb 0.9 is significantly outdated

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

    xcb 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 ordered-float 1.0 is outdated

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

    ordered-float versions

  • Dependency xcb-util 0.3 is a bit outdated

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

    xcb-util 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").

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

    Maintenance status field docs

• aitch

  • Dependency bytes 0.4 is significantly outdated

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

    bytes versions

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency http 0.1 is significantly outdated

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

    http versions

  • Dependency hyper 0.12 is significantly outdated

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

    hyper versions

  • Dependency mime_guess 1.8.5 is significantly outdated

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

    mime_guess versions

  • Dependency tiny_http 0.6.0 is significantly outdated

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

    tiny_http versions

  • Dependency tokio-threadpool 0.1 has issues

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

    tokio-threadpool crate

  • 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

  • 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

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["web-programming::http-server"] 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 = ["http-request", "http-server", "hyper-server", "handler", "middleware"] (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.

• cnx-contrib

  • Dependency alsa 0.5.0 is significantly outdated

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

    alsa versions

  • Dependency async-stream 0.2 is significantly outdated

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

    async-stream versions

  • Dependency nix 0.20.0 is significantly outdated

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

    nix versions

  • Dependency byte-unit 4.0.12 is outdated

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

    byte-unit versions

  • Dependency reqwest 0.11 is outdated

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

    reqwest versions

  • Dependency sioctl 0.0.1 is slightly outdated

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

    sioctl 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

• sioctl

  • Dependency nix 0.17 is significantly outdated

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

    nix versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

• factori, sioctl, factori-impl, sndio-sys

  • 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

• factori-impl

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

• sndio-sys

  • Dependency bindgen 0.53 is significantly outdated

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

    bindgen versions

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "sndio" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

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