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.

• fdt-rs

  • Dependency memoffset 0.5.4 is significantly outdated

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

    memoffset versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/rs-embedded/fdt-rs.git 38d62b97088b8a8d1626177cb9e87ee7e9896df2.

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Dependency fallible-iterator 0.2 is outdated

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

    fallible-iterator versions

  • Dependency num-derive 0.3 is outdated

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

    num-derive versions

  • Dependency rustc_version 0.2 is outdated

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

    rustc_version versions

  • Imprecise dependency requirement static_assertions = 1

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

    static_assertions versions

• fdtdump

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

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

    Easy way to bump dependencies: cargo install cargo-edit; cargo upgrade -i; Also check out Dependabot service on GitHub.

    clap versions

• endian-type-rs

  • Dependency num 0.2.1 is outdated

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

    num versions

• endian-type-rs, fdtdump, localloc

  • 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

• localloc

  • README missing from the repository

    We've searched https://gitlab\.com/ertos/localloc\.git and could not find a README file there.

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

  • License MIT / Apache-2.0 is not in SPDX syntax

    Use OR instead of /.

    SPDX license list

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