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.

• ideas

  • 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 clap 3.0.0-beta.2 is significantly outdated

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

    clap versions

  • Dependency crossterm 0.19 is significantly outdated

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

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

    crossterm versions

  • Dependency failure 0.1.8 has issues

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

    failure crate

  • Dependency minimad 0.7.0 is significantly outdated

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

    minimad versions

  • Dependency termimad 0.10.0 is significantly outdated

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

    termimad versions

  • Dependency defer 0.1.0 is outdated

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

    defer versions

  • Latest stable release is old

    It's been over 4 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

• megenginelite-rs

  • Dependency async-channel 1 is outdated

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

    async-channel versions

  • Dependency ndarray 0.15 is outdated

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

    ndarray versions

  • Imprecise dependency requirement async-channel = 1

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

    async-channel versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["caching"] 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 = ["megenginelite", "dynamic", "load", "model", "safety"] (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.

• megenginelite-sys

  • Missing categories

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

    List of available categories

  • Dependency bindgen 0.59 is significantly outdated

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

    bindgen versions

  • *-sys crate without links property

    If this crate uses C libraries with public symbols, consider adding links = "megenginelite" 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.

  • Dependency libloading 0.7 is outdated

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

    libloading versions

  • Missing keywords

    Help users find your crates. Add keywords = ["megenginelite", "dynamic", "version", "auto-load", "dont"] (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.

• megenginelite-rs, megenginelite-sys, megenginelite-derive

  • README missing from crate tarball

    Cargo sometimes fails to package the README file. Ensure the path to the README in Cargo.toml is valid, and points to a file inside the crate's directory.

• megenginelite-rs, megenginelite-sys, megenginelite-derive

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

• megenginelite-derive

  • Dependency syn 1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = 1

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

    syn versions

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