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.
quick_pswd
Failed to verify create's content against its repository
Verified 4 out of 9 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
- warning: Could not find Cargo.toml for this package in its repo (via tags).
Files in the crates.io crate compared to the repository:
Cargo.lock
does not match the repository.CHANGELOG.md
does not match the repository.README.md
does not match the repository.Cargo.toml.orig
does not match the repository.src/
lib.rs
does not match the repository.main.rs
does not match the repository.
Fetched
https://github.com/08820048/quick_pswd.git
taggedv1.0.3
(d508a4c67cff99e45c23f1e6eafd8319606d84ee).Checked on 2024-07-24
This check is experimental.
- warning: The crates.io package has no commit hash associated with it.
Dependency ansi_term 0.12.1 has issues
It may not be actively developed any more. Consider changing the dependency.
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.
docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
Docs.rs doesn't need to run or even link any code, so system dependencies can simply be skipped. You can also set
cfg()
flags just for docs.rs and use them to hide problematic code.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.Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
In Cargo, different 0.x versions are considered incompatible, so this is a semver-major upgrade.
xpwd
Dependency ansi_term 0.12.1 has issues
It may not be actively developed any more. Consider changing the dependency.
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.
docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
Dependency colored 2.1.0 is a bit outdated
Consider upgrading to 3.0.0 to get all the fixes and improvements.
Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
Failed to verify create's content against its repository
Verified 9 out of 11 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: There is no matching git tag containing version '1.0.4'.
- 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:
README.md
does not match the repository.main.rs
does not match the repository.
Fetched
https://github.com/08820048/xpwd.git
4d94ac1c88fdf7fc38f094e2ffaa48519867f1aa.Checked on 2024-07-24
- warning: The crates.io package has no commit hash associated with it.
digitshield
Failed to verify create's content against its repository
Verified 5 out of 8 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
- warning: Could not find Cargo.toml for this package in its repo (via tags).
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.main.rs
does not match the repository.
Fetched
https://github.com/08820048/digitshield.git
e053a5f87b4392cc955041fdcb2138604432e08b.Checked on 2024-07-28
- warning: The crates.io package has no commit hash associated with it.
Dependency ansi_term 0.12.1 has issues
It may not be actively developed any more. Consider changing the dependency.
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.
docs.rs build failed
docs.rs site failed to build the crate, so users will have trouble finding the documentation. Docs.rs supports multiple platforms and custom configurations, so you can make the build work even if normal crate usage has special requirements.
Dependency colored 2.1.0 is a bit outdated
Consider upgrading to 3.0.0 to get all the fixes and improvements.
Dependency rand 0.8.5 is a bit outdated
Consider upgrading to 0.9.0 to get all the fixes and improvements.
untools
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.
Failed to verify create's content against its repository
Verified 16 out of 18 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
- warning: Could not find any matching commit in the repository. Used latest commit as a fallback. The results may be incorrect.
- warning: There is no matching git tag containing version '1.0.10'.
- 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.Cargo.toml.orig
does not match the repository.README.md
does not match the repository.
Fetched
https://github.com/08820048/uutools.git
1514bbc0d643dc0df06a519c7f09f8dfe33b5828.Checked on 2024-07-24
- warning: The crates.io package has no commit hash associated with it.
If some of these crates are unmaintained and shouldn't be checked, yank them or add [badges.maintenance]
to their
status = "deprecated"Cargo.toml
.