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.

• cargo-update

  • Dependency clap 3.2 is significantly outdated

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

    clap versions

  • Dependency embed-resource 2.4 is significantly outdated

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

    embed-resource versions

  • Dependency home =0.5.9 is significantly outdated

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

    home versions

  • Locked dependency version home =0.5.9

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    home versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.71, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• https

  • Failed to verify create's content against its repository

    Verified 2 out of 6 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • error: Manifest properties don't match: Number of [[bin]] inconsistent; published=2; orig=3; ed=Set(E2015).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.
    • build.rs does not match the repository.
    • README.md does not match the repository.

    Fetched https://github.com/thecoshman/http.git tagged v2.1.0 (272f2c69a30a860c775d11e819993424421b53b7).

    Checked on 2024-09-24

    This check is experimental.

    Forum thread

• febug

  • Failed to verify create's content against its repository

    Verified 4 out of 7 files (includes 2 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • warning: Repository fetch error: cannot fetch a specific object from the remote repository; class=Invalid (3).

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • Cargo.toml not found.
    • build.rs exists, but elsewhere in the repo.
    • lib.rs exists, but elsewhere in the repo.

    Fetched https://git.sr.ht/~nabijaczleweli/febug tagged v1.0.1 (ac31831994ef52074600093b8ff0cdde361aecde).

    Checked on 2025-02-16

    Forum thread

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.36, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• embed-resource

  • Dependency winreg 0.52 is significantly outdated

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

    winreg versions

• https, febug, bidir-map

  • 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

• checksums

  • Dependency blake2 0.9 is significantly outdated

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

    blake2 versions

  • Dependency crc 1.8 is significantly outdated

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

    crc versions

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency futures-cpupool 0.1 has issues

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

    futures-cpupool crate

  • Dependency md-5 0.9 is significantly outdated

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

    md-5 versions

  • Dependency whirlpool 0.9 is outdated

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

    whirlpool versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.51, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• openalias

  • Dependency crc 1.5 is significantly outdated

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

    crc versions

  • Dependency embed-resource 1.1 is significantly outdated

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

    embed-resource versions

  • Dependency peg 0.5 is significantly outdated

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

    peg versions

  • Dependency rustfmt 0.9 has issues

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

    rustfmt crate

  • 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 clap 2.26 is outdated

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

    clap versions

  • Dependency hickory-resolver 0.24 is a bit outdated

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

    hickory-resolver versions

• gen-epub-book

  • Dependency mime_guess 1.8 is significantly outdated

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

    mime_guess versions

  • Dependency reqwest 0.9 is significantly outdated

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

    reqwest versions

  • Dependency url 1.7 is significantly outdated

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

    url versions

  • Dependency uuid 0.7 is significantly outdated

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

    uuid versions

  • Dependency zip 0.4 is significantly outdated

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

    zip versions

  • Dependency clap 2.32 is outdated

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

    clap versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.46, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• pir-8-emu

  • Dependency arraydeque 0.4 is significantly outdated

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

    arraydeque versions

  • Dependency dirs 2.0 is significantly outdated

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

    dirs versions

  • Dependency embed-resource 1.2 is significantly outdated

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

    embed-resource versions

  • Dependency time 0.1 is significantly outdated

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

    time versions

  • Dependency downcast-rs 1.0 is slightly outdated

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

    downcast-rs versions

  • Dependency toml 0.5 is outdated

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

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

    It's an opportunity to update it to the current Rust edition.

    Maintenance status field docs

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.33, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• mail-core-ng

  • Dependency failure 0.1.2 has issues

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

    failure crate

  • Dependency futures 0.1.24 has issues

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

    futures crate

  • Dependency futures-cpupool 0.1.5 has issues

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

    futures-cpupool crate

  • Dependency log 0.3.8 is significantly outdated

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

    log versions

  • Dependency rand 0.3.15 is significantly outdated

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

    rand versions

  • Dependency media-type 0.4.0-unstable is slightly outdated

    Consider upgrading to 0.4.1-unstable to get all the fixes and improvements.

    media-type versions

  • Failed to verify create's content against its repository

    Verified 39 out of 40 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 868c8315813ea80b99f5dbd9da8468b254656d20, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.6.3'.
    • warning: Repository fetch error: cannot fetch a specific object from the remote repository; class=Invalid (3).
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.
    • Cargo.toml.orig does not match the repository.

    Fetched https://git.sr.ht/~nabijaczleweli/mail-core.crate tagged v0.6.3 (95a81a902837ef8ed68a562c1e911335ae51ee5b).

    Checked on 2024-08-04

    Forum thread

  • Missing categories

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

• mail-headers-ng

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency nom 3.1.0 is significantly outdated

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

    nom versions

  • Dependency total-order-multi-map 0.4.5 has issues

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

    total-order-multi-map crate

  • Dependency media-type 0.4.0-unstable is slightly outdated

    Consider upgrading to 0.4.1-unstable to get all the fixes and improvements.

    media-type versions

  • Failed to verify create's content against its repository

    Verified 47 out of 49 files (includes 1 Cargo-generated).

    • warning: Crate tarball has been published from the commit 7e0db7cb5e5189d70b83e78abe396329ad083f2a, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v0.6.7'.
    • error: Cargo.toml parse error: Duplicate Cargo.toml.orig?.
    • error: Cargo.toml and Cargo.toml.orig had different [features]
    • error: Dependencies don't match: 'chrono' is missing in the original Cargo.toml.
      • Make sure to commit and tag after updating Cargo.toml
    • error: Dependencies don't match: 'failure' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'mail-internals' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'media-type' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'nom' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'quoted-string' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'serde' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'soft-ascii-string' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'total-order-multi-map' is missing in the original Cargo.toml.
    • error: Dependencies don't match: 'vec1' is missing in the original Cargo.toml.
    • error: Manifest properties don't match: package.name.
      • If you have a monorepo, you can use git tags in format cratename/v0.6.7
    • warning: Repository fetch error: cannot fetch a specific object from the remote repository; class=Invalid (3).

    Files in the crates.io crate compared to the repository:

    • Cargo.toml exists, but elsewhere in the repo.
    • Cargo.toml.orig does not match the repository.

    Fetched https://git.sr.ht/~nabijaczleweli/mail-headers.crate tagged v0.6.7 (6c303f85d31250bb4200bff137f75bff71807403).

    Checked on 2024-07-28

    Forum thread

  • Imprecise dependency requirement soft-ascii-string = 1

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

    soft-ascii-string versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["email", "header", "mail-headers", "impl", "macro-use"] (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.

• mail-internals-ng

  • Dependency base64 0.6.0 is significantly outdated

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

    base64 versions

  • Dependency failure 0.1.1 has issues

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

    failure crate

  • Dependency idna 0.1.4 is significantly outdated

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

    idna versions

  • Dependency media-type-impl-utils 0.3.0-unstable has issues

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

    media-type-impl-utils crate

  • Dependency nom 3.1.0 is significantly outdated

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

    nom versions

  • Dependency percent-encoding 1.0.0 is significantly outdated

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

    percent-encoding versions

  • Dependency media-type 0.4.0-unstable is slightly outdated

    Consider upgrading to 0.4.1-unstable to get all the fixes and improvements.

    media-type versions

  • Dependency quoted_printable 0.4.0 is outdated

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

    quoted_printable versions

  • Missing categories

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

    List of available categories

• feembox

  • Dependency memmap 0.7 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.

    memmap crate

  • Dependency feed-rs 0.2 is significantly outdated

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

    feed-rs versions

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency mailparse 0.12 is significantly outdated

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

    mailparse versions

  • Dependency clap 2.33 is outdated

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

    clap versions

  • Dependency hostname 0.3 is a bit outdated

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

    hostname 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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.47, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• yaxpeax-superh

  • Dependency bitflags 1.3 is outdated

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

    bitflags versions

  • Dependency yaxpeax-arch 0.2.4 is outdated

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

    yaxpeax-arch versions

  • Failed to verify create's content against its repository

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

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v1.0.1'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Repository fetch error: cannot fetch a specific object from the remote repository; class=Invalid (3).
      • Ooops? If this shouldn't happen, file a bug https://gitlab.com/lib.rs/main

    Fetched https://git.sr.ht/~nabijaczleweli/yaxpeax-superh bae1d17b61629aef1eb67905120480c223f377ed.

    Checked on 2025-02-16

    Forum thread

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.46, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• owapi

  • Dependency reqwest 0.5 is significantly outdated

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

    reqwest versions

  • Dependency serde 0.9 is significantly outdated

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

    serde versions

  • Dependency serde_derive 0.9 is significantly outdated

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

    serde_derive versions

  • Dependency serde_json 0.9 is significantly outdated

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

    serde_json versions

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

    Maintenance status field docs

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

    More info

• bear-lib-terminal, gen-epub-book

  • 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

• trivial_colours

  • Dependency kernel32-sys 0.2 has issues

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

    kernel32-sys crate

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency winapi 0.2 has issues

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

    winapi crate

  • Latest stable release is old

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

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

    More info

• termimage

  • Dependency image 0.24 is outdated

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

    image versions

  • Failed to verify create's content against its repository

    Partially verified 29 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from a different commit than the commit tagged by git tag 'v1.2.1'.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock not found.

    Fetched https://github.com/nabijaczleweli/termimage.git 4867d51b1c9730604a28f0e3e53580f4089dacb8.

    Checked on 2024-08-10

    Forum thread

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.51, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• wcxhead

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["plugin", "winapi", "reserved", "codes"] (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.

• not-stakkr

  • Missing categories

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

    List of available categories

  • 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 chrono 0.2 is significantly outdated

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

    chrono versions

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency regex 0.1 is significantly outdated

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

    regex versions

  • Dependency rustc-serialize 0.3 has issues

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

    rustc-serialize crate

  • Dependency toml 0.2 is significantly outdated

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

    toml versions

  • Latest stable release is old

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

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

    More info

  • 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

  • Dependency clap 2.11 is outdated

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

    clap versions

  • Dependency egg-mode 0.4 is significantly outdated

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

    egg-mode versions

• tweetr

  • Dependency chrono 0.2 is significantly outdated

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

    chrono versions

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency regex 0.1 is significantly outdated

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

    regex versions

  • Dependency rustc-serialize 0.3 has issues

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

    rustc-serialize crate

  • Dependency toml 0.2 is significantly outdated

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

    toml versions

  • Latest stable release is old

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

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

    More info

  • 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

  • Dependency clap 2.13 is outdated

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

    clap versions

  • Dependency egg-mode 0.4 is significantly outdated

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

    egg-mode versions

• codepage-437

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

    Maintenance status field docs

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

    More info

• wustc

  • Missing categories

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

    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

• bloguen

  • Dependency comrak 0.6 is significantly outdated

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

    comrak versions

  • Dependency crc 1.8 is significantly outdated

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

    crc versions

  • Dependency jetscii 0.4 is significantly outdated

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

    jetscii versions

  • Dependency rand 0.7 is significantly outdated

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

    rand versions

  • Dependency rand_xorshift 0.2 is significantly outdated

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

    rand_xorshift versions

  • Dependency uuid 0.7 is significantly outdated

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

    uuid 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

  • Dependency clap 2.33 is outdated

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

    clap versions

  • Dependency toml 0.5 is outdated

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

    toml 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

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.36, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• flac-bound

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.34, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• vswhom-sys

  • *-sys crate without links property

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

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["text-editors", "external-ffi-bindings"] in your Cargo.toml.

    List of available categories

• bear-lib-terminal-sys

  • 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

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

    More info

• bidir-map

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

    Maintenance status field docs

• termimage, checksums, pir-8-emu

  • Dependency clap 2.33 is outdated

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

    clap versions

• poke-a-mango

  • Dependency chrono 0.2 is significantly outdated

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

    chrono versions

  • Dependency conrod 0.47 has issues

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

    conrod crate

  • Dependency cursive 0.3 is significantly outdated

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

    cursive versions

  • Dependency glutin 0.7 is significantly outdated

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

    glutin versions

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency pistoncore-window 0.23 is significantly outdated

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

    pistoncore-window versions

  • Dependency rand 0.3 is significantly outdated

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

    rand versions

  • Dependency regex 0.1 is significantly outdated

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

    regex versions

  • Dependency rustc-serialize 0.3 has issues

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

    rustc-serialize crate

  • Dependency rusttype 0.2 is significantly outdated

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

    rusttype versions

  • Dependency tabwriter 0.1 is significantly outdated

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

    tabwriter versions

  • Dependency toml 0.2 is significantly outdated

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

    toml versions

  • Latest stable release is old

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

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

    More info

  • Dependency clap 2.19 is outdated

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

    clap versions

  • Missing categories

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

    List of available categories

• dumplingh

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency reqwest 0.8 is significantly outdated

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

    reqwest versions

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

    Maintenance status field docs

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

    More info

  • Dependency clap 2.27 is outdated

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

    clap versions

• rfsapi

  • Dependency hyper 0.11 is significantly outdated

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

    hyper versions

  • Dependency time 0.1 is significantly outdated

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

    time versions

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

    Maintenance status field docs

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

    More info

• whereami

  • Dependency gcc 0.3 has issues

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

    gcc crate

  • Latest stable release is old

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

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

    More info

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.37, which is newer than the last 2015-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    The Edition Guide

• blake, checksums

  • 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

• registry-pol

  • Dependency nom 3.2 is significantly outdated

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

    nom versions

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

    Maintenance status field docs

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

    More info

• dishub

  • Missing categories

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

    List of available categories

  • Dependency chrono 0.2 is significantly outdated

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

    chrono versions

  • Dependency hyper 0.9 is significantly outdated

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

    hyper versions

  • Dependency json 0.11 is significantly outdated

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

    json versions

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency regex 0.1 is significantly outdated

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

    regex versions

  • Dependency rustc-serialize 0.3 has issues

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

    rustc-serialize crate

  • Dependency toml 0.2 is significantly outdated

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

    toml versions

  • Latest stable release is old

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

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

    More info

  • 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

  • Dependency clap 2.18 is outdated

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

    clap versions

  • Dependency discord 0.7 is slightly outdated

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

    discord versions

• pls

  • Dependency rust-ini 0.10 is significantly outdated

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

    rust-ini 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

• md6

  • 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

• doh

  • Dependency itertools 0.6 is significantly outdated

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

    itertools versions

  • Dependency kernel32-sys 0.2 has issues

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

    kernel32-sys crate

  • Dependency lazy_static 0.2 is significantly outdated

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

    lazy_static versions

  • Dependency reqwest 0.8 is significantly outdated

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

    reqwest versions

  • Dependency time 0.1 is significantly outdated

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

    time versions

  • Dependency url 1.5 is significantly outdated

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

    url versions

  • Dependency winapi 0.2 has issues

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

    winapi crate

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

    Maintenance status field docs

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

    More info

  • Dependency clap 2.26 is outdated

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

    clap versions

  • Dependency getch 0.2 is outdated

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

    getch versions

• vswhom

  • 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

  • Needs more categories

    Please more specific categories that describe functionality of the crate. Expand categories = ["development-tools::ffi", "text-editors", "external-ffi-bindings"] in your Cargo.toml.

    List of available categories

• tcplistener-accept-timeout

  • Dependency windows-sys 0.52 is outdated

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

    windows-sys versions

No issues found in: hrx safe-transmute

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