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.

• libos

  • Dependency bootloader 0.6.4 is significantly outdated

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

    bootloader versions

  • Dependency x86_64 0.7.5 is significantly outdated

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

    x86_64 versions

  • Latest stable release is old

    It's been over 2 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").

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

• libvmm

  • Latest stable release is old

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

• libvmm_macros

  • 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 regular file inside the crate's directory.

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