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.
lazycc
Failed to verify create's content against its repository
Verified 5 out of 10 files (includes 2 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
Files in the crates.io crate compared to the repository:
Cargo.lock
does not match the repository.Cargo.toml.orig
does not match the repository.README.md
does not match the repository.src/
hook.rs
does not match the repository.main.rs
does not match the repository.prompt.rs
does not match the repository.
Fetched
https://gitlab.com/ogarcia/lazycc.git
tagged0.1.0
(ec903eb7b7f57d6534b27df052fdeb6dc3f293d6).Checked on 2024-08-04
This check is experimental.
- warning: The crates.io package has no commit hash associated with it.
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.
Dependency inquire 0.6 is outdated
Consider upgrading to 0.7.5 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
lesspass-client
Dependency lesspass 0.4 is slightly outdated
Consider upgrading to 0.5.0 to get all the fixes and improvements.
Imprecise dependency requirement tokio = 1
Cargo does not always pick latest versions of dependencies! Specify the version as
tokio = "1.44.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.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.