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.

• pyxel

  • Dependency derivative 1.0.2 is significantly outdated

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

    derivative versions

  • Dependency hex 0.3.2 is significantly outdated

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

    hex versions

  • Dependency image 0.22.0 is significantly outdated

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

    image versions

  • Dependency semver 0.9.0 is outdated

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

    semver versions

  • Dependency zip 0.5.2 is outdated

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

    zip versions

  • Latest stable release is old

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

  • Published crate contains binary files

    The crate contains binary files (Zip file). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

No issues found in: tmx

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