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.

• thiserror_string_context

  • Dependency thiserror 1.0 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

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["error-handling", "context", "string", "thiserror"] (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.

• molar

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "molar" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

    This is also needed to protect your crate from duplicate older versions of itself. C symbols are global, and duplicate symbols can cause all sorts of breakage.

• thiserror_string_context_macro

  • Published crate doesn't match its repository

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

    Looked for the crate in src/thiserror_string_context_macro/. Fetched https://github.com/yesint/thiserror_string_context.git a3b1d9969d90ed939074e386f83688ea3d5b416b.

    Checked on 2024-09-15

    This check is experimental.

    Forum thread

  • No readme property

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

• molar_python

  • Dependency numpy 0.23.0 is outdated

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

    numpy versions

  • Dependency pyo3 0.23.3 is outdated

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

    pyo3 versions

• molar_molfile

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "molar_molfile" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

• molar_xdrfile

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "molar_xdrfile" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

• molar_powersasa

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "molar_powersasa" to crate's Cargo.toml to avoid other libraries colliding with them. Note that the links property adds exclusivity to dependency resolution, but doesn't do any linking.

No issues found in: molar_membrane molar_bin molar_gromacs uni_rc_lock

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