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.

• html-purifier

  • Published crate doesn't match its repository

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

    Fetched https://github.com/mehmetcansahin/html-purifier.git 992088628db9cca272c7c5c66c61fe269906aa9a.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency lol_html 1.2.0 is outdated

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

    lol_html versions

• webworker

  • Dependency path-tree 0.1 is outdated

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

    path-tree 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

• waserv

  • Dependency path-tree 0.1 is outdated

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

    path-tree 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").

    Maintenance status field docs

No issues found in: metascraper

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