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.

• xs-lib

  • Failed to verify create's content against its repository

    Verified 3 out of 9 files (includes 3 Cargo-generated).

    • warning: Crate tarball has been published from the commit 62b1667aa17be513eb137bc53a2e0cedcaa8cbc5, which is not in the repository.
      • Create git tags after comitting any changes, and commit changes after bumping versions and running cargo update.
    • warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
    • 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.
    • LICENSE does not match the repository.
    • README.md does not match the repository.
    • Cargo.toml.orig does not match the repository.
    • .gitignore does not match the repository.
    • src/
      • main.rs does not match the repository.
      • lib.rs does not match the repository.

    Fetched https://github.com/cablehead/xs.git 355e3053a335af733d0bb3a46d012fc93221b089.

    Checked on 2024-08-10

    This check is experimental.

    Forum thread

  • Dependency scru128 2.2.0 is outdated

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

    scru128 versions

• cross-stream

  • Dependency bon 2.3 is outdated

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

    bon versions

  • Imprecise dependency requirement cacache = 13

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

    cacache versions

• http-sh

  • Dependency command-fds 0.2.2 is outdated

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

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

    command-fds versions

  • Dependency http 0.2.8 is outdated

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

    http versions

  • Dependency http-serde 1.1.0 is outdated

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

    http-serde versions

  • Dependency hyper 0.14 is outdated

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

    hyper versions

  • Dependency hyper-staticfile 0.9.4 is outdated

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

    hyper-staticfile versions

  • Dependency nix 0.26.2 is outdated

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

    nix versions

  • Dependency rustls 0.21.0 is outdated

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

    rustls versions

  • Dependency rustls-pemfile 1.0.2 is outdated

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

    rustls-pemfile versions

  • Dependency scru128 2.2.0 is outdated

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

    scru128 versions

  • Dependency tokio-rustls 0.24.0 is outdated

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

    tokio-rustls versions

  • Imprecise dependency requirement tokio = 1

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

    tokio versions

No issues found in: nu_plugin_from_sse scru128-cli grader

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