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.

• pgrx-named-columns

  • Published crate doesn't match its repository

    Verified 10 out of 14 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • .idea/
      • pgx-named-columns.iml not found.
      • .gitignore not found.
      • modules.xml not found.
      • vcs.xml not found.

    Fetched https://github.com/edgarogh/pgrx-named-columns.git 53d31a12fccb7e7c2ca942d2d4bcc41c2494a01a.

    Checked on 2025-04-08

    This check is experimental.

    Forum thread

  • Dependency pgrx 0.13.1 is outdated

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

    pgrx versions

• pgx-named-columns

  • Published crate doesn't match its repository

    Verified 8 out of 10 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • README.md does not match the repository.

    Fetched https://github.com/edgarogh/pgx-named-columns.git tagged v0.1.0 (dbea66cc5294e450591befa8ac0dd46077c2d4fb).

    Checked on 2025-04-06

    Forum thread

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

• colissimo_track

  • Missing categories

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

  • Dependency hyper 0.14.20 is outdated

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

    hyper versions

  • Dependency hyper-tls 0.5.0 is outdated

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

    hyper-tls versions

• rowan-nom

  • README missing from the repository

    We've searched https://github\.com/edgarogh/rowan\-nom\.git and could not find a README file there.

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

  • Dependency nom 7.1 is a bit outdated

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

    nom versions

  • Dependency rowan 0.15 is a bit outdated

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

    rowan versions

• typed-dialogflow

  • 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

  • Dependency gcp_auth 0.7 is outdated

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

    gcp_auth versions

  • Dependency reqwest 0.11 is outdated

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

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• colissimo_track, typed-dialogflow, rowan-nom

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

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