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.

• nanocl

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

  • Dependency colored 2.1.0 is a bit outdated

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

    colored versions

  • Dependency tabled 0.16 is outdated

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

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

    tabled versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools"] 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 = ["microservices", "distributed-systems", "orchestration", "virtual-machine", "deployment"] (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.

• bollard-next

  • Dependency bollard-buildkit-proto =0.4.0 is outdated

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

    bollard-buildkit-proto versions

  • Dependency rand 0.8 is a bit outdated

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

    rand versions

  • Dependency thiserror 1.0 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Optional dependency 'tower-service' 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 'tower-service', 'tonic', 'home', 'rustls-native-certs', 'hyper-util', 'rustls-pki-types', 'num', 'rustls-pemfile', 'hyperlocal', 'rand', 'bollard-buildkit-proto', 'rustls', 'hyper-rustls', 'hyper-named-pipe', 'tokio-stream' may have been unintentional.

    Crate features

• bollard-next, bollard-next-stubs, vpnkitrc, metrs_stubs

  • Missing categories

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

    List of available categories

• bollard-next-stubs

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

  • Locked dependency version bollard-buildkit-proto =0.4.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.

    bollard-buildkit-proto versions

  • Dependency bollard-buildkit-proto =0.4.0 is outdated

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

    bollard-buildkit-proto versions

  • Imprecise dependency requirement bytes = 1

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

    bytes versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api-client", "async-client", "stub", "bollard", "api-version"] (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 'bytes' 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 'bytes', 'bollard-buildkit-proto', 'base64', 'prost' may have been unintentional.

    Crate features

• metrsd_client

  • Missing categories

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

    List of available categories

  • Dependency thiserror 1 is a bit outdated

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

    thiserror versions

  • Missing keywords

    Help users find your crates. Add keywords = ["api-client", "daemon", "microservices", "metrics", "metrs"] (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.

• nutils

  • Failed to verify create's content against its repository

    Verified 1 out of 13 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: Could not find Cargo.toml for this package in its repo (via tags).
    • warning: Could not discover crate's location in its repository (via tags).

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

    • Cargo.toml.orig does not match the repository.
    • readme.md does not match the repository.
    • src/
      • logger.rs exists, but elsewhere in the repo.
      • http_client_error.rs exists, but elsewhere in the repo.
      • http_error.rs exists, but elsewhere in the repo.
      • io_error.rs exists, but elsewhere in the repo.
      • lib.rs exists, but elsewhere in the repo.
    • src/ntex/
      • swagger.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
    • src/ntex/middlewares/
      • serialize_error.rs exists, but elsewhere in the repo.
      • mod.rs exists, but elsewhere in the repo.
      • versioning.rs exists, but elsewhere in the repo.

    Fetched https://github.com/next-hat/nanocl.git tagged ncddns-0.1.1 (a6b278667e8959eb6a6b1b66f4110921dd1485a7).

    Checked on 2024-07-24

    This check is experimental.

    Forum thread

  • Missing categories

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

    List of available categories

  • Dependency ntex 0.6.7 is significantly outdated

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

    ntex versions

  • Dependency utoipa 3.2 is significantly outdated

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

    utoipa versions

  • Dependency bollard-next 0.14.9 is outdated

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

    bollard-next versions

  • Dependency env_logger 0.10.0 is outdated

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

    env_logger versions

  • Dependency utoipa-swagger-ui 3.1 is outdated

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

    utoipa-swagger-ui versions

  • Missing keywords

    Help users find your crates. Add keywords = ["io-error", "middleware", "ntex", "nanocl", "http"] (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.

• metrs_stubs

  • Dependency sysinfo 0.32 is significantly outdated

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

    sysinfo versions

  • Imprecise dependency requirement serde = 1

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

    serde versions

  • Missing keywords

    Help users find your crates. Add keywords = ["shared-data", "metrics", "stub", "api-client", "microservices"] (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.

• ntex-multipart

  • Dependency twoway 0.2 has issues

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

    twoway crate

• nanocl, ntex-files, ntex-identity, ntex-multipart, ntex-session, vpnkitrc, metrsd_client

  • Imprecise dependency requirement ntex = 2

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

    ntex versions

• bollard-next-buildkit-proto

  • Failed to verify create's content against its repository

    Verified 1 out of 35 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: Could not find Cargo.toml for this package in its repo (via tags).
    • warning: Could not discover crate's location in its repository (via tags).
    • warning: Had to perform fuzzy search of the head branch due to lack of commit information in the package.
    • error: Manifest properties don't match: Number of [[bin]] inconsistent; published=2; orig=0; ed=Set(E2021).

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

    • Cargo.toml.orig does not match the repository.
    • README.md does not match the repository.
    • build.rs exists, but elsewhere in the repo.
    • Cargo.lock not found.
    • resources/fsutil/types/
      • stat.proto exists, but elsewhere in the repo.
      • wire.proto exists, but elsewhere in the repo.
    • gogo.proto exists, but elsewhere in the repo.
    • resources/google/protobuf/
      • any.proto exists, but elsewhere in the repo.
      • timestamp.proto exists, but elsewhere in the repo.
      • descriptor.proto exists, but elsewhere in the repo.
    • status.proto exists, but elsewhere in the repo.
    • health.proto exists, but elsewhere in the repo.
    • resources/moby/buildkit/v1/
      • control.proto exists, but elsewhere in the repo.
      • secrets.proto exists, but elsewhere in the repo.
    • policy.proto exists, but elsewhere in the repo.
    • worker.proto exists, but elsewhere in the repo.
    • resources/moby/filesync/v1/
      • auth.proto exists, but elsewhere in the repo.
      • filesync.proto exists, but elsewhere in the repo.
    • upload.proto exists, but elsewhere in the repo.
    • ops.proto exists, but elsewhere in the repo.
    • lib.rs does not match the repository.
    • src/bin/
      • gen.rs exists, but elsewhere in the repo.
      • fetch.rs exists, but elsewhere in the repo.
    • src/generated/
      • moby.buildkit.v1.types.rs exists, but elsewhere in the repo.
      • moby.filesync.v1.rs exists, but elsewhere in the repo.
      • pb.rs exists, but elsewhere in the repo.
      • grpc.health.v1.rs exists, but elsewhere in the repo.
      • google.rpc.rs exists, but elsewhere in the repo.
      • google.protobuf.rs exists, but elsewhere in the repo.
      • moby.buildkit.secrets.v1.rs exists, but elsewhere in the repo.
      • moby.buildkit.v1.rs exists, but elsewhere in the repo.
      • moby.buildkit.v1.sourcepolicy.rs exists, but elsewhere in the repo.
      • moby.upload.v1.rs exists, but elsewhere in the repo.
      • fsutil.types.rs exists, but elsewhere in the repo.

    Fetched https://github.com/fussybeaver/bollard.git 49d38ba1723dd845c001f729dfee4eb017d6dbee.

    Checked on 2024-07-24

    Forum thread

  • Dependency tonic 0.11 is significantly outdated

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

    tonic versions

  • Dependency tonic-build 0.11 is significantly outdated

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

    tonic-build versions

  • Dependency prost 0.12 is outdated

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

    prost versions

  • Dependency prost-types 0.12 is significantly outdated

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

    prost-types versions

  • Dependency ureq 2.9.6 is a bit outdated

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

    ureq versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["generated", "proto", "protobuf", "definition", "buildkit"] (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 'tonic-build' 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 'tonic-build', 'ureq' may have been unintentional.

    Crate features

• ntex-files, ntex-identity, ntex-multipart, ntex-session

  • Dependency derive_more 0.99 is outdated

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

    derive_more versions

• ntex-files, ntex-identity, ntex-multipart, ntex-session

  • Using outdated edition for no reason

    We estimate that this crate requires at least Rust 1.75, 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

• nanocl_utils

  • Dependency utoipa-swagger-ui 8.0 is outdated

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

    utoipa-swagger-ui versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["os::unix-apis"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["nanocl", "ntex", "networking", "versioning", "logging"] (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 'nanocl_error' 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 'nanocl_error' may have been unintentional.

    Crate features

• nanocl_error, nanocld, nutils, nerror

  • Dependency serde_yaml 0.9 has issues

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

    serde_yaml crate

• nanocl_stubs

  • Imprecise dependency requirement utoipa = 5

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

    utoipa versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["data-model", "vm", "orchestration", "nanocl", "api-client"] (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.

• nerror

  • Failed to verify create's content against its repository

    Verified 1 out of 7 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: Could not find Cargo.toml for this package in its repo (via tags).
    • warning: Could not discover crate's location in its repository (via tags).

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

    • Cargo.toml.orig does not match the repository.
    • readme.md exists, but elsewhere in the repo.
    • src/
      • io.rs exists, but elsewhere in the repo.
      • http.rs exists, but elsewhere in the repo.
      • http_client.rs exists, but elsewhere in the repo.
      • lib.rs exists, but elsewhere in the repo.

    Fetched https://github.com/next-hat/nanocl.git 952df4302395cd54d1c93059e36036a95e5f3894.

    Checked on 2024-08-04

    Forum thread

  • Dependency bollard-next 0.15.4 is outdated

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

    bollard-next versions

  • Dependency ntex 0.7.7 is outdated

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

    ntex versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["error", "io", "conversion", "nanocl", "http"] (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.

• ntex-identity, ntex-multipart, ntex-session

  • Missing categories

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

    List of available categories

• nanocld

  • Failed to verify create's content against its repository

    Could not check any files

    • warning: The crates.io package has no information about its path inside its repository.
    • error: Repository doesn't exist: Can't checkout the repository. It's either gone or private: remote authentication required but no callback set; class=Http (34); code=Auth (-16).
      • Make sure the repository URL in Cargo.toml is correct and works with git clone. The repository must be public.

    Checked on 2024-08-04

    Forum thread

  • Dependency ntex 0.6.3 is significantly outdated

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

    ntex versions

  • Dependency bollard-next 0.14.1 is outdated

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

    bollard-next versions

  • Dependency env_logger 0.10 is outdated

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

    env_logger versions

  • Dependency hyper 0.14.24 is outdated

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

    hyper versions

  • Dependency jsonschema 0.16.1 is outdated

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

    jsonschema versions

  • Dependency metrsd_client 0.1.1 is slightly outdated

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

    metrsd_client versions

  • Dependency nanocl_stubs 0.3.0 is outdated

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

    nanocl_stubs versions

  • Dependency thiserror 1.0.37 is a bit outdated

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

    thiserror versions

  • Imprecise dependency requirement url = 2

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

    url versions

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["development-tools", "network-programming"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["container", "daemon", "store", "orchestrator", "events"] (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.

• vpnkitrc

  • Missing keywords

    Help users find your crates. Add keywords = ["unix-socket", "tcp-udp", "docker", "desktop", "client"] (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.

• nanocld_client

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["api-client", "distributed-systems", "nanocl", "daemon", "container"] (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.

• nanocl_error

  • Missing categories

    Categories improve browsing of lib.rs and crates.io. Add categories = ["web-programming::http-client"] to the Cargo.toml.

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["error", "io-error", "nanocl", "conversion", "diesel"] (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.

• nanocld_client, nanocl_utils, nanocl_error

  • Imprecise dependency requirement ntex = 2

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

    ntex versions

• metrsd

  • Dependency ntex 0.6.3 is significantly outdated

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

    ntex versions

  • Dependency sysinfo 0.27.7 is significantly outdated

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

    sysinfo versions

  • Dependency env_logger 0.10.0 is outdated

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

    env_logger versions

  • Dependency metrs_stubs 0.1.0 is a bit outdated

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

    metrs_stubs versions

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["host", "microservices", "metrics", "metrs", "daemon"] (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.

• metrs

  • Missing categories

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

    List of available categories

  • Missing keywords

    Help users find your crates. Add keywords = ["host", "metrics", "microservices", "daemon", "real-time"] (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.

• nutils, nerror, bollard-next-buildkit-proto

  • 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

No issues found in: nanocl-client nanocl-models

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