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.

• matrix-sdk-indexeddb

  • docs.rs build failed

    docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.

    Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set cfg() flags just for docs.rs and use them to hide problematic code.

    Detecting docs.rs

  • Dependency getrandom 0.2.15 is outdated

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

    getrandom versions

  • Dependency indexed_db_futures 0.5.0 is outdated

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

    indexed_db_futures versions

  • Missing keywords

    Help users find your crates. Add keywords = ["indexed-db", "matrix-sdk", "storage-back-end", "web-storage"] (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.

  • Optional dependency 'growable-bloom-filter' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Feature 'growable-bloom-filter' may have been unintentional.

    Crate features

• cargo-unleash

  • Dependency structopt 0.3.9 has issues

    It has been losing active users, which may be a sign it's deprecated or obsolete. Consider replacing it with a different crate.

    structopt crate

  • Latest prerelease is old

    It's been over 3 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").

    Users pay attention to the latest release date. Even if the crate is perfectly fine as-is, users may not know that.

    Maintenance status field docs

  • Dependency cargo 0.59.0 is significantly outdated

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

    cargo versions

  • Dependency toml_edit 0.13.0 is significantly outdated

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

    toml_edit versions

  • Imprecise dependency requirement anyhow = 1

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

    anyhow versions

  • Dependency flexi_logger 0.22 is outdated

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

    flexi_logger versions

  • Dependency git2 0.13.23 is significantly outdated

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

    git2 versions

  • Dependency petgraph 0.6 is outdated

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

    petgraph versions

  • Failed to verify create's content against its repository

    Partially verified 21 files (includes 3 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: There is no matching git tag containing version '1.0.0-alpha.dev'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Files in the crates.io crate compared to the repository:

    • Cargo.lock does not match the repository.
    • Cargo.toml.orig does not match the repository.

    Fetched https://github.com/gnunicorn/cargo-unleash.git a802cd8619b7cd253f1dc45a800951ad4eee489e.

    Checked on 2024-08-04

    This check is experimental.

    Forum thread

• substrate-wasmtime

  • Dependency cfg-if 0.1.9 is significantly outdated

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

    cfg-if versions

  • Dependency target-lexicon 0.10.0 is significantly outdated

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

    target-lexicon versions

  • Dependency wasmparser 0.59.0 is significantly outdated

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

    wasmparser versions

  • Dependency wasmtime-environ 0.19.0 is significantly outdated

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

    wasmtime-environ versions

  • Dependency wasmtime-jit 0.19.0 is significantly outdated

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

    wasmtime-jit versions

  • Dependency wasmtime-runtime 0.19.0 is significantly outdated

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

    wasmtime-runtime versions

  • 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

  • Dependency region 2.2.0 is outdated

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

    region versions

  • Dependency wasmtime-profiling 0.19.0 is outdated

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

    wasmtime-profiling versions

  • 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 = ["wasmtime", "wasm-module", "linker", "wasm-memory", "high-level"] (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.

• matrix-sdk-store-media-cache-wrapper

  • Failed to verify create's content against its repository

    Verified 2 out of 4 files (includes 1 Cargo-generated).

    • warning: The crates.io package has no commit hash associated with it.
      • Publish a new version, without using --allow-dirty flag. Make sure all changes are committed before publishing. Use include/exclude in Cargo.toml to omit unnecessary files.
    • warning: The crates.io package has no information about its path inside its repository.
    • warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: There is no matching git tag containing version '0.1.1'.
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.

    Files in the crates.io crate compared to the repository:

    • Cargo.toml.orig does not match the repository.
    • lib.rs exists, but elsewhere in the repo.
    • lib.rs does not match the repository.

    Looked for the crate in native/media-cache-wrapper/. Fetched https://github.com/acterglobal/a3.git 7ee80f3370a17bdb3d1c08debafc7b106d81552b.

    Checked on 2024-08-04

    Forum thread

  • Imprecise dependency requirement serde_json = 1

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

    serde_json versions

  • Dependency matrix-sdk-base 0.7.0 is outdated

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

    matrix-sdk-base versions

  • Dependency matrix-sdk-store-encryption 0.7.0 is outdated

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

    matrix-sdk-store-encryption versions

  • Dependency ruma-common 0.12.1 is significantly outdated

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

    ruma-common versions

  • Dependency ruma-events 0.27.11 is outdated

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

    ruma-events versions

• matrix-sdk-sled

  • Dependency derive_builder 0.11.2 is significantly outdated

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

    derive_builder versions

  • Dependency dashmap 5.2.0 is outdated

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

    dashmap versions

  • Dependency matrix-sdk-base 0.6.0 is outdated

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

    matrix-sdk-base versions

  • Dependency matrix-sdk-common 0.6.0 is outdated

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

    matrix-sdk-common versions

  • Dependency matrix-sdk-crypto 0.6.0 is outdated

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

    matrix-sdk-crypto versions

  • Dependency matrix-sdk-store-encryption 0.2.0 is outdated

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

    matrix-sdk-store-encryption versions

  • Dependency ruma 0.7.0 is outdated

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

    ruma versions

  • Dependency thiserror 1.0.30 is outdated

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

    thiserror versions

  • Missing keywords

    Help users find your crates. Add keywords = ["matrix-sdk", "storage-back-end", "native", "encryption", "sled"] (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.

• matrix-sdk-store-encryption

  • Dependency getrandom 0.2.15 is outdated

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

    getrandom versions

  • Dependency rand 0.8.5 is outdated

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

    rand versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["encryption", "matrix-sdk", "encrypted-storage", "key-value-store", "storage-key"] (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.

• matrix-sdk-indexeddb, matrix-sdk-sled, matrix-sdk-store-media-cache-wrapper

  • Missing categories

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

    List of available categories

• cargo-unleash, matrix-sdk-sled, matrix-sdk-store-media-cache-wrapper, multicodec

  • 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

• matrix-sdk-qrcode

  • Missing categories

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

    List of available categories

• sc-sync-state-rpc, substrate-wasmtime-jit, substrate-wasmtime-profiling, reference-trie, substrate-wasmtime-runtime, sc-tracing-proc-macro, pallet-generic-asset, sp-phragmen, sc-client

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

• dadada

  • Dependency pulldown-cmark 0.5.3 is significantly outdated

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

    pulldown-cmark versions

  • Dependency clap 2.33.0 is outdated

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

    clap 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

• multicodec

  • Dependency failure 0.1 has issues

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

    failure crate

  • Dependency unsigned-varint 0.2 is significantly outdated

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

    unsigned-varint 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

  • Missing categories

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

    List of available categories

• substrate-serializer, substrate-primitives, sr-std, sp-tasks, pallet-benchmark, sp-election-providers, sc-finality-grandpa-warp-sync, pallet-mmr-primitives, sp-phragmen-compact

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

• matrix-sdk-appservice, matrix-sdk-ffi, matrix-sdk-crypto-ffi, acter-ffi, acter, acter-cli, acter-tui, matrix-sdk-bot, matrix-sdk-agent, agent-smith

  • Crate is 'reserved'

    Please be respectful of crates.io and don't squat crate names.

    It's OK if you intend to publish this project in the near future. Keep in mind that even if you have good intentions, things may not go as planned. crates.io won't reclaim abandoned crates, so reserving good names may end up wasting the good names.

• matrix-sdk-bot, matrix-sdk-agent, agent-smith

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