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.

• fnsql

  • Dependency tempdir ^0.3 has issues

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

    tempdir crate

  • Dependency sqlx ^0.8 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.

    sqlx versions

• enum_macro_gen

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-09-22

    This check is experimental.

    Forum thread

  • Dependency syn ^1.0 is significantly outdated

    Upgrade to 3.0.3 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

  • Dependency convert_case ^0.6 is outdated

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

    convert_case versions

• fnsql, ptytest, interact, enum_macro_gen, casserole, boxing-arena, fnsql-macro, interact_prompt, interact_derive, casserole-derive

  • License MIT/Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

• casserole

  • Dependency rust-crypto ^0.2 has issues

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

    rust-crypto crate

  • Imprecise dependency requirement serde_json = ^1

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

    serde_json versions

  • Dependency thiserror ^1 is outdated

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

    thiserror versions

  • 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

• interact

  • Dependency ron ^0.4 is significantly outdated

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

    ron versions

• interact, boxing-arena, interact_prompt, interact_derive

  • Latest stable release is old

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

• interact_prompt

  • Dependency ansi_term ^0.11 has issues

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

    ansi_term crate

  • Dependency rustyline ^6.1 is significantly outdated

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

    rustyline versions

• fnsql-macro

  • Dependency syn ^1.0 is significantly outdated

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

    syn versions

• interact_derive

  • Dependency proc-macro2 ^0.4 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote ^0.6 is significantly outdated

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

    quote versions

  • Dependency syn ^0.15 is significantly outdated

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

    syn versions

• casserole-derive

  • Dependency syn 1.0.* is significantly outdated

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

    syn versions

  • Imprecise dependency requirement lazy_static = ^1

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

    lazy_static versions

  • 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

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