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.

• sprattus

  • Dependency futures-util-preview ^0.3.0-alpha.19 has issues

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

    futures-util-preview crate

  • Dependency parking_lot 0.9.0 is significantly outdated

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

    parking_lot versions

  • Dependency tokio ^0.2.0-alpha.6 has issues

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

    tokio crate

  • Dependency tokio-postgres ^0.5.0-alpha.1 is significantly outdated

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

    tokio-postgres versions

  • 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.

  • Dependency strfmt 0.1.6 is outdated

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

    strfmt versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'postgres', which isn't a category we recognize

    lib.rs has simplified and merged some of crates.io categories. Please file a bug if we got it wrong.

    List of available categories

  • Latest stable release is old

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

  • Missing keywords

    Help users find your crates. Add keywords = ["async-orm", "postgresql", "postgres", "primary-key", "table"] (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.

  • 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.

• sprattus-derive

  • Dependency syn 1.0.5 is significantly outdated

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

    syn versions

  • 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.

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'postgres', which isn't a category we recognize

    List of available categories

  • Latest stable release is old

    It's been over 5 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").

    Maintenance status field docs

  • 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.

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