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.

• robots_txt

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

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

    Maintenance status field docs

• incrust

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

    Nightly crates tend to have a short lifespan. We're delisting them if they're not updated frequently.

    Maintenance status field docs

  • Dependency log 0.3 is significantly outdated

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

    log versions

  • Dependency maplit 0.1 is significantly outdated

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

    maplit 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

• rsmorphy

  • Dependency base64 0.9 is significantly outdated

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

    base64 versions

  • Dependency env_logger 0.5 is significantly outdated

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

    env_logger versions

  • Dependency string_cache 0.7 is significantly outdated

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

    string_cache versions

  • Latest stable release is old

    It's been over 6 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

  • Dependency num 0.2 is outdated

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

    num versions

• smart-string

  • Imprecise dependency requirement serde = 1

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

    This crate does not bump semver-minor when adding new features, so to be safe you get all the features/APIs/fixes that your crate depends on, require a more specific patch version.

    serde versions

  • Published crate doesn't match its repository

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

    Fetched https://github.com/irbis-labs/smart-string.git 23402f1f3ee43077991031a26e0b148ae1fe4160.

    Checked on 2024-07-28

    This check is experimental.

    Forum thread

• incrust, rsmorphy, rsmorphy-dict-ru, rsmorphy-dict-uk, kreida

  • 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

• robots_txt, smart-string, incrust, rsmorphy, kreida

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

    Use OR instead of /.

    SPDX license list

• rsmorphy-dict-ru, rsmorphy-dict-uk, kreida

  • Latest stable release is old

    It's been over 7 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

• rsmorphy-dict-ru

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

• kreida

  • Dependency num 0.1 is significantly outdated

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

    num versions

• rsmorphy-dict-uk

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