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.

• strip-exports

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

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

  • Missing categories

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

  • Missing keywords

    Help users find your crates. Add keywords = ["strip", "export", "wasm"] (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.

• fritzlogger

  • Missing categories

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

    List of available categories

  • Dependency config 0.9 is significantly outdated

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

    In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.

    config versions

  • Dependency error-chain 0.12 has issues

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

    error-chain crate

  • Dependency futures 0.1 has issues

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

    futures crate

  • Dependency md5 0.6 is significantly outdated

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

    md5 versions

  • Dependency once_cell 0.2 is significantly outdated

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

    once_cell versions

  • Dependency reqwest 0.9 is significantly outdated

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

    reqwest versions

  • Dependency roxmltree 0.6 is significantly outdated

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

    roxmltree versions

  • Dependency tokio 0.1 has issues

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

    tokio crate

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

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

    Maintenance status field docs

  • Dependency bitflags 1 is outdated

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

    bitflags versions

  • Dependency clap 2.33 is outdated

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

    clap versions

  • Dependency toml 0.5 is outdated

    Consider upgrading to 1.0.1+spec-1.1.0 to get all the fixes and improvements.

    toml versions

  • Imprecise dependency requirement bitflags = 1

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

    bitflags versions

• pwasm-utils

  • Cryptocurrency crate

    This crate has been classified as related to cyrptocurrencies. If you believe this categorization is a mistake, then please review crate's categories and keywords, or file a bug. If it is related, then please reconsider your choices, and yank it.

    Author of this site is firmly convinced that cryptocurrencies have a net-negative effect on society.

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