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.

• cbor-data

  • Dependency libipld ^0.14 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.

    libipld crate

  • Dependency base64 ^0.13.0 is significantly outdated

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

    base64 versions

  • Dependency half ^1.6.0 is significantly outdated

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

    half versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["encoding"] 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 = ["key-builder", "cbor", "array-builder", "dictionary", "encoder"] (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 'chrono' 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 'chrono' may have been unintentional.

    Crate features

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.60, which is newer than the last 2018-edition compiler. You can upgrade without breaking any compatibility. Run cargo fix --edition and update edition="…" in Cargo.toml.

    Using the latest edition helps avoid old quirks of the compiler, and ensures Rust code has consistent syntax and behavior across all projects.

    The Edition Guide

• swarm-discovery

  • Imprecise dependency requirement thiserror = ^2

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

    thiserror versions

• actyxos_sdk

  • Dependency base64 ^0.12 is significantly outdated

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

    base64 versions

  • Dependency fixed ~0.5 is significantly outdated

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

    fixed versions

  • Dependency multibase ^0.8 is significantly outdated

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

    multibase versions

  • Dependency rusqlite ^0.24 is significantly outdated

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

    rusqlite versions

  • Dependency typenum ~1.12 is significantly outdated

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

    typenum versions

  • Imprecise dependency requirement anyhow = ^1

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

    anyhow versions

  • Dependency derive_more ~0.99 is outdated

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

    derive_more versions

  • Dependency intern-arc ^0.5.0 is a bit outdated

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

    intern-arc versions

  • Dependency reqwest ~0.11 is outdated

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

    reqwest versions

• cbor-bin

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in bin/. Fetched https://github.com/actyx/cbor-data.git e3027ed8c030df42f44ff7a8efba22e465b14dc1.

    Checked on 2025-09-14

    This check is experimental.

    Forum thread

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["cbor", "cbor-data", "properties", "array", "element"] (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.

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• actyxos_sdk, party-types, actyxos_sdk_macros

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

• acto

  • Dependency smol_str ^0.1.23 is significantly outdated

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

    smol_str versions

• party-types

  • Missing categories

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

    List of available categories

  • Imprecise dependency requirement anyhow = ^1

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

    anyhow versions

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

  • 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

  • Missing keywords

    Help users find your crates. Add keywords = ["multi-party", "session", "hosting", "projection"] (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.

• intern-arc

  • Missing categories

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

    List of available categories

• pure-stage

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

• actyxos_sdk, batch_queue, actyxos_sdk_macros

  • 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

• fbr_cache

  • Dependency intrusive-collections ^0.9.4 is a bit outdated

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

    intrusive-collections versions

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

    Maintenance status field docs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["replace", "cache", "frequency-based", "lru", "strategy"] (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.

• cbor-data-derive

  • Published crate doesn't match its repository

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

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

    • Cargo.lock not found.

    Looked for the crate in derive/. Fetched https://github.com/actyx/cbor-data.git 7ea232db363af490cfb9fb323d69ab4de3a3afd6.

    Checked on 2025-06-01

    Forum thread

  • Dependency syn ^1 is significantly outdated

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

    syn versions

  • Imprecise dependency requirement syn = ^1

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

    syn versions

  • No readme property

    Specify path to a README file for the project, so that information about is included in the crates.io tarball.

• actyx_sdk_macros

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

  • Dependency syn ^1.0.58 is significantly outdated

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

    syn versions

  • 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

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

    Maintenance status field docs

• actyxos_sdk_macros

  • Dependency syn ~1.0 is significantly outdated

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

    syn versions

• netsim-embed-macros

  • Dependency rand ^0.8.5 is outdated

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

    rand versions

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

• actyx

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

• actyx, ax_server, ax_lsp, ax_rpc, ax_rope, ax_client

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

• ax_server, ax_lsp, ax_rpc, ax_rope, ax_client

  • Crate contains junk files

    The crate contains boilerplate Rust files with no real functionality.

• ax

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/ax ) failed. Please try again later.

• ax_core

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/ax_core ) failed. Please try again later.

• actyx_sdk

  • Internal error

    We couldn't check this crate at this time, because: timed out validating Origin( lib.rs/crates/actyx_sdk ). Please try again later.

• actyxos_data_flow

  • Internal error

    We couldn't check this crate at this time, because: Validation of Origin( lib.rs/crates/actyxos_data_flow ) failed. Please try again later.

No issues found in: sync_wrapper

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