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.

• vrl

  • Dependency ansi_term 0.12 has issues

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

    ansi_term crate

  • Dependency convert_case 0.7.1 is significantly outdated

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

    convert_case versions

  • Dependency serde_yaml 0.9.34 has issues

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

    serde_yaml crate

  • Dependency sha-1 0.10 has issues

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

    sha-1 crate

  • Dependency domain 0.10.4 is outdated

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

    domain versions

  • Dependency nom 7 is a bit outdated

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

    nom versions

  • Dependency ordered-float 4 is outdated

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

    ordered-float versions

  • Dependency prost-reflect 0.14 is outdated

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

    prost-reflect 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 csv = 1

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

    csv versions

• dd-rust-license-tool

  • Dependency cargo_metadata 0.18 is outdated

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

    cargo_metadata versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from the commit bdee29ab918b40ad870fa89c553092b1d0f4d867, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
      • Make sure to commit and tag after bumping the version number.
    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v1.0.3'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Fetched https://github.com/datadog/rust-license-tool.git e552188523f0b8831870ad8cce6869fb21333b43.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

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