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.

• plt

  • Dependency ndarray 0.15 is outdated

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

    ndarray versions

• plt, plt-draw, tline

  • Dependency thiserror 1.0 is a bit outdated

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    thiserror versions

• plt-cairo

  • Dependency cairo-rs 0.16 is significantly outdated

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

    cairo-rs versions

  • Imprecise dependency requirement anyhow = 1

    Cargo does not always pick latest versions of dependencies! Specify the version as anyhow = "1.0.98". If Cargo.lock ends up having an unexpectedly old version of the dependency, you might get a dependency that lacks features/APIs or important bugfixes that you depend on. This is most likely to happen when using the minimal-versions flag, used by users of old Rust versions.

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    anyhow versions

• tline

  • Dependency indicatif 0.16 is significantly outdated

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

    indicatif versions

  • Dependency ndarray 0.15 is outdated

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

    ndarray 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

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