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.

• mzsignal

  • Imprecise dependency requirement thiserror = >=2

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

    thiserror versions

  • Dependency ndarray >=0.15.6,<0.16 is outdated

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

    ndarray versions

  • Dependency ndarray-linalg 0.16.0 is outdated

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

    ndarray-linalg versions

  • Optional dependency 'ndarray' 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 'ndarray', 'rayon', 'ndarray-linalg' may have been unintentional.

    Crate features

• thermorawfilereader

  • 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

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Dependency flatbuffers 23.5.26 is outdated

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

    flatbuffers versions

  • Missing keywords

    Help users find your crates. Add keywords = ["thermorawfilereader", "file-reader", "config"] (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.

• mzdata

  • Dependency quick-xml 0.30 is significantly outdated

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

    quick-xml versions

  • Dependency ndarray 0.15.6 is outdated

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

    ndarray versions

  • Dependency rusqlite 0.31.0 is outdated

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

    rusqlite versions

  • Imprecise dependency requirement regex = 1

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

    regex versions

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

    Crate features

• mzdeisotope

  • 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

• mzdeisotope, mzdeisotoper, mzdeisotope-map

  • Imprecise dependency requirement thiserror = 2

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

    thiserror versions

• mzdeisotope, mzdeisotoper, mzdeisotope-map

  • Dependency itertools 0.12.0 is significantly outdated

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

    itertools versions

• mzsvg

  • Dependency fontdb 0.18.0 is significantly outdated

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

    fontdb versions

  • Dependency svg2pdf 0.11.0 is significantly outdated

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

    svg2pdf versions

  • Dependency resvg 0.42.0 is outdated

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

    resvg versions

  • Optional dependency 'resvg' 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 'resvg', 'svg2pdf', 'fontdb' may have been unintentional.

    Crate features

• dotnetrawfilereader-sys

  • Dependency thiserror 1.0.63 is a bit outdated

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

    thiserror versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["dotnetrawfilereader-sys", "run-time", "dotnetrawfilereader"] (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 readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

  • Published crate contains binary files

    The crate contains binary files (Windows DLL). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• mzpeaks

  • Imprecise dependency requirement rayon = 1

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

    rayon versions

  • Missing categories

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

    List of available categories

• chemical_elements

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["pattern", "composition", "element", "element-specification"] (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.

• numpress-rs

  • License BSD-3-Clause-Clear/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

No issues found in: mzdata-spectra

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