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.
stelae
Published crate doesn't match its repository
Verified 126 out of 128 files (includes 2 Cargo-generated).
- warning: Crate tarball has been published from a commit that is not in the main branch (searched 7 commits deep).
Files in the crates.io crate compared to the repository:
OVERVIEW.md
not found..env
not found.
Fetched
https://github.com/openlawlibrary/stelae.git
taggedv0.4.2
(7be0323b25e42ddc29ebf752ee97e990289e7b81).Checked on 2025-04-27
This check is experimental.
Dependency derive_more 0.99.17 is outdated
Upgrade to 2.0.1 to get all the fixes, and avoid causing duplicate dependencies in projects.
Easy way to bump dependencies:
cargo install cargo-edit; cargo upgrade -i
; Also check out Dependabot service on GitHub.Dependency git2 0.18 is outdated
Upgrade to 0.20.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 sophia 0.8.0 is outdated
Upgrade to 0.9.0 to get all the fixes, and avoid causing duplicate dependencies in projects.
Dependency sqlx 0.7 is outdated
Upgrade to 0.8.5 to get all the fixes, and avoid causing duplicate dependencies in projects.
Imprecise dependency requirement actix-web = 4
Cargo does not always pick latest versions of dependencies! Specify the version as
actix-web = "4.10.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
.