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.

• youki

  • Dependency wasi-common 31.0.0 is significantly outdated

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

    wasi-common versions

  • Dependency wasmer-wasix 0.9.0 is significantly outdated

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

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

    wasmer-wasix versions

  • Dependency wasmtime 31.0.0 is significantly outdated

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

    wasmtime versions

  • Dependency nix 0.29.0 is significantly outdated

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

    nix versions

  • Dependency procfs 0.17.0 is outdated

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

    procfs versions

  • Dependency wasmer 4.0.0 is outdated

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

    wasmer versions

  • Imprecise dependency requirement tabwriter = 1

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

    tabwriter versions

  • Optional dependency 'wasi-common' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'wasi-common', 'wasmedge-sdk', 'wasmer-wasix', 'wasmer', 'wasmtime' may have been unintentional.

    Crate features

• libcontainer

  • Dependency protobuf = 3.2.0 is significantly outdated

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

    protobuf versions

  • Locked dependency version protobuf = 3.2.0

    This can easily cause a dependency resolution conflict. If you must work around a semver-breaking dependency that can't be yanked, use a range of versions or fork it.

    protobuf versions

  • Dependency nix 0.29.0 is significantly outdated

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

    nix versions

  • Dependency procfs 0.17.0 is outdated

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

    procfs versions

• oci-spec

  • Imprecise dependency requirement regex = 1

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

    regex versions

  • Optional dependency 'quickcheck' 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 'quickcheck' may have been unintentional.

    Crate features

• libcgroups

  • Dependency nix 0.29.0 is significantly outdated

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

    nix versions

  • Dependency procfs 0.17.0 is outdated

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

    procfs versions

  • Optional dependency 'libc' exposed as an implicit feature

    Cargo automatically makes publicly-available crate features for every optional dependency, unless the dependencies are referenced using dep: syntax. Features 'libc', 'rbpf', 'errno', 'libbpf-sys' may have been unintentional.

    Crate features

• youki, liboci-cli, libcontainer, libcgroups

  • Missing categories

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

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