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.

• overridegettersetter

  • Could not fetch repository

    We've had trouble cloning git repo from https://github\.com/jguyet/overridegettersetter\.git

    At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.

  • Dependency log 0.3.6 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 quote 0.3.3 is significantly outdated

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

    quote versions

  • Dependency syn 0.9.0 is significantly outdated

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

    syn versions

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

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

    Maintenance status field docs

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

  • 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

• macroclassrender

  • README missing from the repository

    We've searched https://github\.com/jguyet/macro\-class\-render\.git and could not find a README file there.

  • Dependency quote 0.3.15 is significantly outdated

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

    quote versions

  • Dependency syn 0.11.11 is significantly outdated

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

    syn versions

  • 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

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

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

    More info

• macro-class-render

  • README missing from the repository

    We've searched https://github\.com/jguyet/macro\-class\-render\.git and could not find a README file there.

  • Dependency quote 0.3.15 is significantly outdated

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

    quote versions

  • Dependency syn 0.11.11 is significantly outdated

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

    syn versions

  • 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

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

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

    More info

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