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.

• fastobo-graphs

  • Dependency mashup 0.1.9 has issues

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

    mashup crate

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Optional dependency 'mashup' 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 'mashup', 'fastobo' may have been unintentional.

    Crate features

• textwrap-macros

  • Dependency proc-macro-hack 0.5 has issues

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

    proc-macro-hack crate

  • Latest stable release is old

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

• fastobo

  • Dependency ordered-float 4.0 is outdated

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

    ordered-float versions

  • Optional dependency 'num_cpus' 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 'num_cpus', 'crossbeam-channel', 'lazy_static' may have been unintentional.

    Crate features

• cksfv

  • Dependency assert_cli 0.6.3 has issues

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

    assert_cli crate

  • Dependency textwrap 0.15.1 is significantly outdated

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

    textwrap versions

  • Dependency textwrap-macros 0.2.5 is outdated

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

    textwrap-macros versions

  • Optional dependency 'memmap' 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 'memmap' may have been unintentional.

    Crate features

• fastobo-validator

  • Dependency clap 3.1.0 is significantly outdated

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

    clap versions

  • Dependency textwrap 0.15.1 is significantly outdated

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

    textwrap versions

  • Dependency colored 2.0.0 is a bit outdated

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

    colored versions

  • Dependency isbn 0.2.0 is outdated

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

    isbn versions

  • Dependency itertools 0.10.0 is outdated

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

    itertools versions

  • Latest stable release is old

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

• flips

  • Dependency err-derive 0.2.3 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    err-derive crate

  • 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

• horned-functional

  • Dependency enum_meta 0.6.0 is slightly outdated

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

    enum_meta versions

  • Dependency horned-owl 0.11.0 is outdated

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

    horned-owl versions

  • Dependency thiserror 1.0.0 is outdated

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

    thiserror versions

  • Latest stable release is old

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

• pubchem

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["…"] 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

  • Dependency quick-xml 0.22.0 is significantly outdated

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

    quick-xml versions

  • Dependency thiserror 1.0.30 is outdated

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

    thiserror versions

  • Dependency ureq 2.4.0 is outdated

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

    ureq versions

• psp2-sys, vitallocator, pruefung

  • Latest stable release is old

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

• pruefung

  • Dependency digest ^0.6 is significantly outdated

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

    digest versions

  • Dependency generic-array ^0.8 is significantly outdated

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

    generic-array versions

  • The Cargo package has no git commit information

    Before publishing a package, make sure all packaged files are committed to the repository, and there are no "dirty" files. Push this commit to crate's public repository.

    To protect against supply chain attacks similar to CVE-2024-3094, lib.rs will soon start flagging non-reproducible packages without public source code as suspicious. Currently only git repositories are supported (but may be hosted anywhere, not just GitHub). If you'd like a different SCM supported, please file a feature request.

    More info

  • Missing categories

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

    List of available categories

• lightmotif

  • Dependency rand 0.8.5 is outdated

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

    rand versions

  • Dependency rand_distr 0.4.3 is outdated

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

    rand_distr versions

  • Optional dependency 'rand' 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 'rand', 'rand_distr' may have been unintentional.

    Crate features

• lightmotif-py

  • Dependency pyo3 0.23.0 is outdated

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

    pyo3 versions

  • Optional dependency 'lightmotif-tfmpvalue' 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 'lightmotif-tfmpvalue' may have been unintentional.

    Crate features

• packageurl, lightmotif-io

  • Imprecise dependency requirement memchr = 2

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

    memchr versions

• nanoset-py

  • 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

  • Dependency built 0.3.1 is significantly outdated

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

    built versions

  • Dependency pyo3 0.8.0 is significantly outdated

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

    pyo3 versions

  • Dependency pyo3-built 0.3.0 is outdated

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

    pyo3-built versions

• vitallocator

  • 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

• flips-sys

  • 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

  • *-sys crate without links property

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

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

• nafcodec-py

  • Dependency built 0.7 is outdated

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

    built versions

  • Dependency pyo3 0.23.0 is outdated

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

    pyo3 versions

• fastobo-derive-internal

  • Dependency darling 0.20.1 is outdated

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

    darling versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• psp2-sys

  • *-sys crate without links property

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

• proteinogenic, pubchem, horned-visit

  • Latest stable release is old

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

• horned-visit

  • Dependency blanket 0.2.0 is significantly outdated

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

    blanket versions

  • Dependency horned-owl 0.11.0 is outdated

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

    horned-owl versions

• diced-py

  • Dependency pyo3 0.22.5 is significantly outdated

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

    pyo3 versions

• textwrap-macros-impl

  • Dependency proc-macro-hack 0.5 has issues

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

    proc-macro-hack crate

  • Dependency syn 1.0 is significantly outdated

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

    syn versions

  • Latest stable release is old

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

• embedded-picofont

  • Dependency bitvec 0.19.4 is significantly outdated

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

    bitvec versions

  • Dependency embedded-graphics 0.6.0 is significantly outdated

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

    embedded-graphics versions

• lightmotif-transfac

  • Dependency lightmotif 0.6.0 is outdated

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

    lightmotif versions

  • Dependency lightmotif-io 0.6.0 is outdated

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

    lightmotif-io versions

• uniprot

  • Dependency quick-xml 0.30.0 is significantly outdated

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

    quick-xml versions

  • Optional dependency 'num_cpus' 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 'num_cpus', 'url', 'crossbeam-channel', 'lazy_static' may have been unintentional.

    Crate features

• obofoundry

  • Failed to verify create's content against its repository

    Partially verified 11 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no information about its path inside its repository.

    Fetched https://github.com/althonos/obofoundry.rs.git tagged v0.11.0 (fd3c785871038a004891e1201c1ddb7c5c461e3c).

    Checked on 2025-04-30

    This check is experimental.

    Forum thread

No issues found in: fastobo-owl lightmotif-tfmpvalue nafcodec pyo3-built diced blanket fastobo-syntax

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