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.

• colored

  • Dependency windows-sys >=0.48,<=0.59 is outdated

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

    windows-sys versions

  • Missing categories

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

• rspec

  • Dependency clippy 0.0.153 has issues

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

    clippy crate

  • Dependency derive_builder 0.9 is significantly outdated

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

    derive_builder versions

  • Dependency time 0.2 is significantly outdated

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

    time versions

  • Dependency colored 2.0 is a bit outdated

    Consider upgrading to 3.0.0 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.

    colored versions

  • Dependency derive-new 0.5 is outdated

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

    derive-new versions

• systemd-parser

  • 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 itertools ^0.5 is significantly outdated

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

    itertools versions

  • Dependency nom ^2.0 is significantly outdated

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

    nom versions

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

  • Dependency quick-error ^1.1 is outdated

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

    quick-error versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["systemd", "nom", "parser"] (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.

• systemd-linter

  • Incorrect dependency requirement systemd-parser = ^0.1

    We could not parse it. Please check the semver syntax.

    Cargo used to be more forgiving about the semver syntax, so it's possible that an already-published crate doesn't satisfy the current rules.

    Cargo dependencies manual

  • 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 colored ^1.0 is significantly outdated

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

    colored versions

  • Dependency clap ^2.20 is outdated

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

    clap versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["systemd", "linter", "lint", "system-d", "unit-file"] (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.

• to_string, systemd-parser, systemd-linter

  • 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

• to_string, systemd-parser, systemd-linter

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

    If the crate is truly stable, why not make a 1.0.0 release?

    Maintenance status field docs

• plop565613631

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

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

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