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.

• spop, pwgen2, vpn-kill-switch, hfile, zsmtp, permesi, httpwsrep, httpredis, grpc-status

  • Imprecise dependency requirement anyhow = ^1

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

• slick, gbump

  • Imprecise dependency requirement clap = ^4

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

    clap versions

• gbump

  • Dependency git2 ^0.20 is outdated

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

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

    git2 versions

• httpwsrep

  • Dependency clap ^3.1 is significantly outdated

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

    clap versions

  • Dependency mysql_async ^0.29 is significantly outdated

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

    mysql_async versions

  • Dependency prometheus ^0.13 is outdated

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

    prometheus versions

  • Dependency warp ^0.3 is a bit outdated

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

    warp versions

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

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

• permesi

  • Dependency opentelemetry ^0.27 is significantly outdated

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

    opentelemetry versions

  • Dependency opentelemetry-otlp ^0.27 is significantly outdated

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

    opentelemetry-otlp versions

  • Dependency opentelemetry_sdk ^0.27 is significantly outdated

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

    opentelemetry_sdk versions

  • Dependency tracing-opentelemetry ^0.28 is significantly outdated

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

    tracing-opentelemetry versions

  • Dependency utoipa-swagger-ui ^8 is significantly outdated

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

    utoipa-swagger-ui versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency axum ^0.7 is outdated

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

    axum versions

  • Dependency built ^0.7 is outdated

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

    built versions

  • Dependency rand ^0.8.5 is outdated

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

    rand versions

  • Dependency reqwest ^0.12 is outdated

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

    reqwest versions

  • Dependency sqlx ^0.8 is a bit outdated

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

    sqlx versions

  • Dependency tonic ^0.12 is outdated

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

    tonic versions

  • Dependency tower-http ^0.6 is slightly outdated

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

    tower-http versions

  • Dependency ulid ^1.1 is slightly outdated

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

    ulid versions

• zsmtp

  • Dependency serde_yaml ^0.9 has issues

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

    serde_yaml crate

• hfile

  • Dependency bytesize ^1 is outdated

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

    bytesize versions

  • Dependency md5 ^0.7 is outdated

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

    md5 versions

• assemble

  • Dependency git2 ^0.13 is significantly outdated

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

    git2 versions

  • Dependency serde_yaml ^0.8 has issues

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

    serde_yaml crate

  • Latest stable release is old

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

  • Dependency compound_duration ^1 is outdated

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

    compound_duration versions

• httpredis

  • Dependency tokio-util ^0.6 is significantly outdated

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

    tokio-util versions

  • Dependency rand ^0.8 is outdated

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

    rand versions

  • Dependency warp ^0.3 is a bit outdated

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

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

    Maintenance status field docs

• dbquota

  • Dependency clap ^2 is significantly outdated

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

    clap versions

  • Dependency mysql ^16.0 is significantly outdated

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

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

    Maintenance status field docs

  • Imprecise dependency requirement clap = ^2

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

    clap versions

• immortal

  • Dependency clap ^2 is significantly outdated

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

    clap versions

  • Dependency rustc-serialize ^0.3 has issues

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

    rustc-serialize crate

  • Dependency time ^0.1 is significantly outdated

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

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

    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

  • Imprecise dependency requirement clap = ^2

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

    clap versions

• httpredis, assemble, grpc-status

  • Dependency clap ^2.33 is significantly outdated

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

    clap versions

• grpc-status

  • Dependency prost ^0.7 is significantly outdated

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

    prost versions

  • Dependency tonic ^0.4 is significantly outdated

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

    tonic versions

  • Dependency tonic-build ^0.4 is significantly outdated

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

    tonic-build 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").

    Maintenance status field docs

• pg_exporter

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/pg_exporter ) failed. Please try again later.

• cron-when

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/cron-when ) failed. Please try again later.

• ssh-vault

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/ssh-vault ) failed. Please try again later.

• pgmon

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/pgmon ) failed. Please try again later.

• s3m

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/s3m ) failed. Please try again later.

• epazote

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/epazote ) failed. Please try again later.

• s3m-core

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/s3m-core ) failed. Please try again later.

• backup

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/backup ) failed. Please try again later.

• dbpulse

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/dbpulse ) failed. Please try again later.

• pxs

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/pxs ) failed. Please try again later.

• mariadb_exporter

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/mariadb_exporter ) failed. Please try again later.

• s3mon

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/s3mon ) failed. Please try again later.

• gruezi

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/gruezi ) failed. Please try again later.

• policyd-rate-limit

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/policyd-rate-limit ) failed. Please try again later.

No issues found in: dsn fork cron-parser compound_duration

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