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.

• apns

  • Incorrect dependency requirement byteorder = *

    We could not parse it. Please check the semver syntax.

    Cargo used to be more forgiving about the semver syntax, so it's possible that an already-published crate doesn't satisfy the current rules.

    Cargo dependencies manual

  • Incorrect dependency requirement num = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Incorrect dependency requirement openssl = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Incorrect dependency requirement rand = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Incorrect dependency requirement rustc-serialize = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Incorrect dependency requirement time = *

    We could not parse it. Please check the semver syntax.

    Cargo dependencies manual

  • Latest stable release is old

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

  • Missing categories

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

  • Dependency rustc-serialize * has issues

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

    rustc-serialize crate

  • Dependency time * has issues

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

    time crate

  • 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

  • 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

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