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.

• lambda-runtime-types

  • Dependency aws-config 0.52 is significantly outdated

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

    aws-config versions

  • Dependency aws-sdk-secretsmanager 0.22 is significantly outdated

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

    aws-sdk-secretsmanager versions

  • Dependency lambda_runtime 0.7 is significantly outdated

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

    lambda_runtime versions

  • Imprecise dependency requirement anyhow = 1

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

• cargo-patch

  • Dependency cargo 0.72 is significantly outdated

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

    cargo versions

  • Dependency toml 0.7 is significantly outdated

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

    toml versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • 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

  • Failed to verify create's content against its repository

    Partially verified 19 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: The crates.io package has no information about its path inside its repository.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock does not match the repository.
    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/itmettkede/cargo-patch.git tagged v0.3.2 (5075f0ea7d1ec523dd050cb6ef70b72d6d3bc993).

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

• tenable

  • Dependency bytes 0.5 is significantly outdated

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

    bytes versions

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

    More info

  • Dependency http 0.2 is outdated

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

    http versions

• minify

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

    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

• serde_single_or_vec, tenable

  • 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

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