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.

• fae

  • Latest stable release is old

    It's been over 5 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 font8x8 ^0.2.5 is significantly outdated

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

    font8x8 versions

  • Dependency png ^0.15.3 is significantly outdated

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

    png versions

  • Dependency rusttype ^0.8.2 is outdated

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

    rusttype versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["rendering::graphics-api"] 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 = ["fragment-shaders", "draw", "fae"] (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.

• minreq

  • Dependency rustls 0.21.1 is outdated

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

    rustls versions

  • Dependency rustls-native-certs 0.6.1 is outdated

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

    rustls-native-certs versions

  • Dependency rustls-webpki 0.101.0 is outdated

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

    rustls-webpki versions

  • Dependency webpki-roots 0.25.2 is outdated

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

    webpki-roots versions

  • Optional dependency 'openssl' 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 'openssl', 'webpki-roots', 'serde', 'base64', 'rustls-webpki', 'native-tls', 'rustls-native-certs', 'rustls', 'serde_json', 'openssl-probe' may have been unintentional.

    Crate features

• fontdue-sdl2

  • 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 = ["fontdue-sdl2", "sdl2", "fontdue", "sdl2-ttf"] (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.

• stperf

  • 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

  • Latest stable release is old

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

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