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.

• dyer-cli, dyer, streamer

  • 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

• crossbus

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

    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 async-std ^1.12.0 has issues

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

    async-std crate

  • Published crate doesn't match its repository

    Verified 88 out of 89 files (includes 3 Cargo-generated).

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

    • Cargo.lock not found.
    • runner does not match the repository.

    Fetched https://github.com/hominee/crossbus.git 0bf68407cad16e4270b2029e9855919d4f7982bd.

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Published crate contains binary files

    The crate contains binary files (WOFF font). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

• dyer

  • Dependency base64 ^0.13.0 is significantly outdated

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

    base64 versions

  • Dependency signal-hook ^0.1.17 is significantly outdated

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

    signal-hook versions

  • Dependency http ^0.2.5 is outdated

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

    http versions

  • Dependency hyper ^0.14.20 is outdated

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

    hyper versions

  • Dependency hyper-tls ^0.5.0 is outdated

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

    hyper-tls versions

  • Published crate contains binary files

    The crate contains binary files (WOFF font). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.

    Audit page

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.61, which is newer than the last 2018-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

• dyer-cli, dyer, telegra-ph, streamer, dyer-macros

  • 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

• telegra-ph

  • Incorrect category

    Crate's categories property in Cargo.toml contains 'api', 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

• streamer

  • Dependency hyper ^0.14.19 is outdated

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

    hyper versions

• crossbus-derive

  • Latest prerelease 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

  • Published crate doesn't match its repository

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

    Looked for the crate in derive/. Fetched https://github.com/hominee/crossbus.git e1b86fccfd087967035587628fe3d4ba62efe10c.

    Checked on 2024-08-10

    Forum thread

• dyer-macros

  • 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

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