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.

• fproxy

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Dependency libloading 0.8.9 is a bit outdated

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

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

    libloading versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools::ffi"] 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 = ["plugin-system", "unstable-abi", "stable-abi", "generator", "dll"] (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.

• fproxy_derive

  • No repository property

    Specify git repository URL in Cargo.toml to help users find more information, contribute, and for lib.rs to read more info.

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in fproxy_derive/. Fetched https://github.com/plegeus/fproxy.git 6126caa9ff00b57f92c639cacc02548c7b1d7f7c.

    Checked on 2025-10-31

    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.

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