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.

• cacao

  • Latest prerelease is old

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

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Dependency infer 0.15 is significantly outdated

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

    infer versions

  • Dependency core-foundation 0.9 is slightly outdated

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

    core-foundation versions

  • Dependency core-graphics 0.23 is outdated

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

    core-graphics versions

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'os::ios-apis', 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

  • Optional dependency 'infer' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'infer', 'uuid' may have been unintentional.

    Crate features

• alchemy-styles

  • Dependency cssparser 0.25.5 is significantly outdated

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

    cssparser versions

  • Dependency proc-macro2 0.4.24 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote 0.6.10 is significantly outdated

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

    quote versions

  • Dependency toml 0.5 is outdated

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

    toml versions

• alchemy

  • Dependency matches is not needed

    matches! macro in the standard library

    matches crate

  • Dependency phf 0.7 is significantly outdated

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

    phf versions

  • Dependency proc-macro-hack 0.5.4 has issues

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

    proc-macro-hack crate

  • Dependency strum 0.15.0 is significantly outdated

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

    strum versions

  • Dependency strum_macros 0.15.0 is significantly outdated

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

    strum_macros versions

  • Imprecise dependency requirement serde_json = 1

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

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency language-tags 0.2.2 is outdated

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

    language-tags versions

  • Dependency toml 0.5 is outdated

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

    toml versions

  • Optional dependency 'alchemy-cocoa' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'alchemy-cocoa' may have been unintentional.

    Crate features

• alchemy-cocoa

  • Dependency cocoa 0.18.4 is significantly outdated

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

    cocoa versions

  • Dependency core-foundation 0.6 is significantly outdated

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

    core-foundation versions

  • Dependency core-graphics 0.17.1 is significantly outdated

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

    core-graphics versions

  • Dependency dispatch 0.1.4 is significantly outdated

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

    dispatch versions

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Detecting docs.rs

• alchemy-styles, alchemy, alchemy-lifecycle, alchemy-cocoa, alchemy-macros

  • 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

• alchemy-macros

  • Dependency ansi_term 0.11.0 has issues

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

    ansi_term crate

  • Dependency lalrpop 0.16.1 is significantly outdated

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

    lalrpop versions

  • Dependency lalrpop-util 0.16.1 is significantly outdated

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

    lalrpop-util versions

  • Dependency proc-macro-hack 0.5.2 has issues

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

    proc-macro-hack crate

  • Dependency proc-macro2 0.4.24 is significantly outdated

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

    proc-macro2 versions

  • Dependency quote 0.6.10 is significantly outdated

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

    quote versions

  • Dependency syn 0.15 is significantly outdated

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

    syn versions

  • Dependency version_check 0.1.5 is significantly outdated

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

    version_check versions

• alchemy-lifecycle

  • Imprecise dependency requirement serde_json = 1

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

    serde_json versions

• appkit-derive

  • Dependency syn 1.0.14 is significantly outdated

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

    syn 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").

    Maintenance status field docs

• appkit

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/ryanmcgrath/appkit\-rs\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

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

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

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