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.

• pmtiles

  • 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 fmmap 0.3 is slightly outdated

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

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

    fmmap versions

  • Dependency thiserror 1 is a bit outdated

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

    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

• ferrostar

  • Dependency android_logger 0.14.1 is significantly outdated

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

    android_logger versions

  • Dependency geo 0.29.3 is outdated

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

    geo versions

  • Dependency getrandom 0.2.15 is outdated

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

    getrandom versions

  • Dependency rand 0.8.5 is a bit outdated

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

    rand versions

  • Dependency uniffi 0.28.3 is outdated

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

    uniffi versions

  • Optional dependency 'serde-wasm-bindgen' 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 'serde-wasm-bindgen', 'web-time', 'getrandom', 'wasm-bindgen' may have been unintentional.

    Crate features

• tile_sorcerer

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

• sdf_glyph_renderer

  • Dependency freetype-rs 0.35.0 is significantly outdated

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

    freetype-rs versions

• pbf_font_tools, sdf_glyph_renderer

  • Dependency thiserror 1.0.41 is a bit outdated

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

    thiserror versions

• b2get

  • Dependency reqwest 0.11.22 is outdated

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

    reqwest versions

• mbtileserver

  • 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 clap 3.1 is significantly outdated

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

    clap versions

  • Dependency libsqlite3-sys 0.24 is significantly outdated

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

    libsqlite3-sys versions

  • Dependency r2d2_sqlite 0.20 is significantly outdated

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

    r2d2_sqlite versions

  • Dependency rusqlite 0.27 is significantly outdated

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

    rusqlite versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency pretty_env_logger 0.4 is outdated

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

    pretty_env_logger versions

  • Dependency tilejson 0.3 is outdated

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

    tilejson versions

  • Imprecise dependency requirement flate2 = 1

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

    flate2 versions

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

  • Missing keywords

    Help users find your crates. Add keywords = ["deprecated", "mbtiles", "60"] (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.

No issues found in: build_pbf_glyphs

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