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.
rustls-platform-verifier-android
Failed to verify create's content against its repository
Verified 3 out of 8 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. Useinclude
/exclude
inCargo.toml
to omit unnecessary files.
- Publish a new version, without using
- warning: Found a Cargo.toml for this package in its repo (via tags), but the version was different.
- 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:
pom.xml
not found.maven-metadata-local.xml
not found.maven/rustls/rustls-platform-verifier/0.1.1/
rustls-platform-verifier-0.1.1.aar
not found._remote.repositories
not found.rustls-platform-verifier-0.1.1.pom
not found.
Looked for the crate in
android-release-support/
. Fetchedhttps://github.com/rustls/rustls-platform-verifier.git
3edb4d278215a8603020351b8b519d907a26041f.Checked on 2024-08-05
This check is experimental.
- warning: The crates.io package has no commit hash associated with it.
Could not fetch repository
We've had trouble cloning git repo from
https://github\.com/rustls/rustls\-platform\-verifier\.git
At the moment we only support git, and attempt fetching when we index a new release. Cloning is necessary for lib.rs to gather data that is missing on crates.io, e.g. to correctly resolve relative URLs in README files, which depend on repository layout and non-standard URL schemes of repository hosts.
README missing from crate tarball
Cargo sometimes fails to package the
README
file. Ensure the path to theREADME
inCargo.toml
is valid, and points to a file inside the crate's directory.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.
Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["os"]
to theCargo.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.
Missing keywords
Help users find your crates. Add
keywords = ["tls-certificates", "android", "operating-system", "jvm", "verification"]
(up to 5) to theCargo.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.Published crate contains binary files
The crate contains binary files (Zip file). Crates are meant to be compiled from source. Please check that you haven't published temporary build files by accident. If you have test fixtures, consider excluding them from crates-io tarball, since Cargo doesn't run tests from crates-io packages.
rustls-platform-verifier
Dependency android_logger 0.13 is significantly outdated
Upgrade to 0.14.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.
Dependency rustls-webpki 0.102 is outdated
Consider upgrading to 0.103.0 to get all the fixes and improvements.
Dependency windows-sys 0.52 is outdated
Upgrade to 0.59.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement security-framework = 3
Cargo does not always pick latest versions of dependencies! Specify the version as
security-framework = "3.2.0"
. IfCargo.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 theminimal-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.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["os"]
to theCargo.toml
.Optional dependency 'android_logger' 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 'android_logger', 'base64', 'jni', 'paste' may have been unintentional.
secret-service
Dependency generic-array 0.14 is slightly outdated
Consider upgrading to 1.2.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.Dependency getrandom 0.2 is outdated
Consider upgrading to 0.3.1 to get all the fixes and improvements.
Imprecise dependency requirement once_cell = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
once_cell = "1.20.0"
. IfCargo.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 theminimal-versions
flag, used by users of old Rust versions.Missing categories
Categories improve browsing of lib.rs and crates.io. Add
categories = ["cryptography"]
to theCargo.toml
.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.