Conversation
Vetting Succeeded (269 fully audited, 1 partially audited, 257 exempted)
It was downloading and compiling binstall in every runner for every CI build. The CI cache isn't working.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
cargo vet, and removetime, whichcargo denyidentified as vulnerable under RUSTSEC-2026-0009, which has had maintenance issues, and which has way too many unsafe blocks.In order to fully excise
time, we replacedbatandoctocrab, which necessitated the creation ofjp_github.Cargo binstall was also rebuilding itself every run, without proper caching, so it was removed. This saved time on shear but we still saw some runs of insta that took more time.