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.

• upend

  • Dependency actix ^0.10 is significantly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    actix versions

  • Dependency actix-files ^0.5 is significantly outdated

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

    actix-files versions

  • Dependency actix-web ^3.3 is significantly outdated

    Consider upgrading to 4.9.0 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.

    actix-web versions

  • Dependency built 0.5.1 is significantly outdated

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

    built versions

  • Dependency env_logger ^0.8 is significantly outdated

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

    env_logger versions

  • Dependency nonempty 0.6.0 is significantly outdated

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

    nonempty versions

  • Dependency opener ^0.5.0 is significantly outdated

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

    opener versions

  • Dependency uuid 0.8 is significantly outdated

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

    uuid versions

  • Dependency actix-multipart 0.3.0 is outdated

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

    actix-multipart versions

  • Dependency actix_derive ^0.5 is outdated

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

    actix_derive versions

  • Dependency bs58 ^0.4 is outdated

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

    bs58 versions

  • Dependency clap 2.33.0 is outdated

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

    clap versions

  • Dependency diesel 1.4 is outdated

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

    diesel versions

  • Dependency diesel_migrations 1.4 is outdated

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

    diesel_migrations versions

  • Dependency filebuffer 0.4.0 is a bit outdated

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

    filebuffer versions

  • Dependency image 0.23.14 is outdated

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

    image versions

  • Dependency lru 0.7.0 is significantly outdated

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

    lru versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Dependency webbrowser ^0.5.5 is outdated

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

    webbrowser versions

  • Dependency webp 0.2.0 is outdated

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

    webp versions

  • Dependency webpage 1.4.0 is a bit outdated

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

    webpage versions

  • Imprecise dependency requirement libsqlite3-sys = ^0

    Cargo does not always pick latest versions of dependencies! Specify the version as libsqlite3-sys = "0.31.0". 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.

    If you want to keep using truly minimal dependency requirements, please make sure you test them in CI with -Z minimal-versions Cargo option, because it's very easy to accidentally use a feature added in a later version.

    libsqlite3-sys versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["database-implementations"] 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 = ["graph-database", "knowledge-management", "personal", "hypertext", "information"] (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.

  • Published crate contains binary files

    The crate contains binary files (WOFF font). 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

• suncalc

  • 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.