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.

• resident-utils

  • Dependency cron 0.13.0 is significantly outdated

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

    cron versions

  • Dependency deadpool-redis 0.18.0 is outdated

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

    deadpool-redis versions

• lineapi, pinterest-api, eventbridge-pipes-events

  • Imprecise dependency requirement serde = 1

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

    serde versions

• spsheet

  • Dependency nom ~3.2.1 is significantly outdated

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

    nom versions

  • Dependency quick-xml ~0.10.1 is significantly outdated

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

    quick-xml versions

  • Dependency tempdir ~0.3.5 has issues

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

    tempdir crate

  • Dependency time ~0.1.38 is significantly outdated

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

    time versions

  • Dependency walkdir ~2.0.1 is significantly outdated

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

    walkdir versions

  • Dependency zip ~0.2.6 is significantly 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 7 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

  • 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

  • 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

• twapi

  • Dependency ipnetwork ~0.17.0 is significantly outdated

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

    ipnetwork versions

  • Dependency twapi-reqwest ^0.2 has issues

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

    twapi-reqwest crate

  • Dependency url ~2.2.1 is significantly outdated

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

    url versions

  • Dependency base64 ~0.13.0 is outdated

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

    base64 versions

  • Imprecise dependency requirement tokio = ^1

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

    tokio versions

• tiktok-business

  • Dependency itertools 0.12 is significantly outdated

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

    itertools versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency strum 0.26 is outdated

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

    strum versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • Optional dependency 'hex' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'hex', 'strum', 'sha2', 'hmac' may have been unintentional.

    Crate features

• tiktokapi-v2

  • Dependency itertools 0.12 is significantly outdated

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

    itertools versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

• dynamodb-mutex

  • Dependency rusoto_core ~0.46.0 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    rusoto_core crate

  • Dependency rusoto_dynamodb ~0.46.0 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    rusoto_dynamodb crate

  • Dependency thiserror ~1.0.24 is a bit outdated

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

    thiserror versions

• eventbridge-pipes-events

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

  • Dependency aws_lambda_events 0.15 is outdated

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

    aws_lambda_events versions

• csv-zip-maker

  • Imprecise dependency requirement thiserror = 1

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

    thiserror versions

  • Dependency zip 0.6.6 is outdated

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

    zip versions

• twapi-ureq

  • Dependency ureq ~2.1.0 is significantly outdated

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

    ureq versions

  • Dependency base64 ~0.13.0 is outdated

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

    base64 versions

  • Dependency bytebuffer ~0.2.1 is outdated

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

    bytebuffer versions

  • Dependency rand ~0.8.3 is a bit outdated

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

    rand versions

• actix-daemon-utils

  • Imprecise dependency requirement actix-rt = ~2

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

    actix-rt 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").

    Maintenance status field docs

• tiktokapi-v2, tiktok-business, csv-zip-maker, eventbridge-pipes-events

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

• twapi-oauth

  • Dependency rand ^0.7 is significantly outdated

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

    rand versions

  • Dependency rust-crypto ^0.2 has issues

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

    rust-crypto crate

  • Dependency base64 ^0.13 is outdated

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

    base64 versions

• pinterest-api

  • Dependency oauth2 4 is a bit outdated

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

    oauth2 versions

  • Failed to verify create's content against its repository

    Partially verified 57 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: There is no matching git tag containing version '0.2.0'.
      • git tag v0.2.0 45deb40abb2b89e83fc23cd6debb247caf9b3358; git push origin --tags

    Fetched https://github.com/aoyagikouhei/pinterest-api-rs.git 45deb40abb2b89e83fc23cd6debb247caf9b3358.

    Checked on 2024-12-08

    Forum thread

• actix-postgres

  • Dependency bb8-postgres ~0.8.0 is outdated

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

    bb8-postgres versions

  • Dependency thiserror ~1.0.30 is a bit outdated

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

    thiserror 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").

    Maintenance status field docs

• twapi, twapi-ureq, twapi-oauth, dynamodb-mutex

  • Latest stable release is old

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

• era-jp

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

    Maintenance status field docs

• redis-batches

  • Dependency redis 0.22 is outdated

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

    redis versions

  • Missing categories

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

• twapi-v2, twapi-reqwest

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

No issues found in: dynamodb-mutex-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.