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.

• address-formatter

  • Dependency enum-map 1 is significantly outdated

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

    enum-map versions

  • Dependency serde_yaml 0.8 has issues

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

    serde_yaml crate

  • Dependency strum 0.23 is significantly outdated

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

    strum versions

  • Dependency strum_macros 0.23 is significantly outdated

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

    strum_macros versions

  • Imprecise dependency requirement anyhow = 1

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

  • Dependency handlebars 4 is outdated

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

    handlebars versions

  • Dependency itertools 0.10 is outdated

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

    itertools 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

  • Missing categories

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

• geos

  • Published crate doesn't match its repository

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

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

    • Cargo.lock does not match the repository.

    Fetched https://github.com/georust/geos.git 783e6176bdedfcae7a9caa1d754188a08fa433ff.

    Checked on 2025-02-09

    This check is experimental.

    Forum thread

  • Dependency wkt 0.10.3 is outdated

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

    wkt versions

  • Optional dependency 'geo-types' 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 'geo-types', 'geojson', 'wkt' may have been unintentional.

    Crate features

• gtfs-structures

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Fetched https://github.com/rust-transit/gtfs-structure.git 03cd946b99494df1a81cfae346ad2012d00b49b6.

    Checked on 2025-02-02

    Forum thread

  • Dependency itertools 0.13 is outdated

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

    itertools versions

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement bytes = 1

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

    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.

    bytes versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["parser-implementations"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["gtfs", "calendar", "location", "read-url", "file"] (up to 5) to the Cargo.toml. Best keywords are alternative terms or their spellings that aren't in the name or description. Also add a keyword that precisely categorizes this crate and groups it with other similar crates.

  • Optional dependency 'reqwest' 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 'reqwest', 'futures' may have been unintentional.

    Crate features

• gtfs-geojson

  • Failed to verify create's content against its repository

    Verified 15 out of 23 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Crate tarball has been published from the commit 604dd7a1f7d0f97f1a89c9b061a41e3094dfd310, 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: Could not discover crate's location in its repository (via tags).
      • Make sure the repository URL in Cargo.toml is correct
    • warning: There is no matching git tag containing version '0.5.0'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Existence of [lib] inconsistent: published=true; orig=false.

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

    • Cargo.lock does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • .github/workflows/
      • tests.yml not found.
      • publish.yml not found.
    • src/
      • lib.rs not found.
      • utility.rs does not match the repository.
      • main.rs does not match the repository.
      • converter.rs does not match the repository.

    Fetched https://gitlab.com/codeursenliberte/gtfs-to-geojson.git fdac4caf29a3b66bf99d8de902c64557e2bf7abd.

    Checked on 2024-08-04

    Forum thread

  • Imprecise dependency requirement serde_json = 1

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

    serde_json versions

  • Dependency gtfs-structures 0.41.0 is a bit outdated

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

    gtfs-structures versions

• cosmogony

  • Dependency geojson 0.22 is significantly outdated

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

    geojson versions

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

    serde versions

  • Dependency osmpbfreader 0.16 is outdated

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

    osmpbfreader versions

• osm_boundaries_utils

  • Dependency geo 0.26.0 is outdated

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

    geo versions

  • Dependency osmpbfreader 0.16 is outdated

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

    osmpbfreader versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["science::geo"] to the Cargo.toml.

    List of available categories

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