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.

• messagepack-rs

  • Reported security advisory RUSTSEC-2021-0092

    Deserialization functions pass uninitialized memory to user-provided Read

    All crate audits

  • Buggy README path

    The non-local path to readme specified as \.\./README\.md exposes a bug in Cargo. Please use a path inside the crate's directory. Symlinks are okay. Please verify the change doesn't break any repo-relative URLs in the README.

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

• dlhn

  • Dependency bigdecimal 0.3.0 is outdated

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

    bigdecimal versions

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.57, 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

• libmonsterengine

  • Dependency hyper 0.13.1 is significantly 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.

    hyper versions

  • Dependency tokio 0.2.5 has issues

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

    tokio crate

  • 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

• plamo

  • 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

• dlhn_derive

  • Dependency syn 1.0.73 is significantly outdated

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

    syn versions

• messagepack-rs-macros

  • Dependency syn 1.0.5 is significantly outdated

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

    syn versions

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