Repository navigation
Audit dependencies with Laravel Vet - #3
Merged
JustSteveKing merged 1 commit intoOct 20, 2026
Merged
Conversation
composer audit only knows published advisories, so a freshly compromised release passes it and the dependency bot would open a PR for it. Laravel Vet closes that gap as a Composer plugin: - vet.json records what has been read; composer install fails on anything else, including a version re-published with other files. - minimum-release-age holds back every release younger than 7 days. juststeveking/* and roave/security-advisories are excluded: the first are first-party, the second has to be current to protect anything. The baseline is today's lock moved back to releases at least a week old, which is why fourteen packages step down a patch or minor (laravel/framework 13.37.0 to 13.35.0, guzzle 8.3.0 to 8.2.0). The dependency bot moves to weekly. Vet refuses the update it writes, so the workflow tolerates that, installs the new lock without the plugin, and puts Vet's report in the PR body. The PR passes CI once vet.json is updated on its branch.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
JustSteveKing
merged commit Oct 20, 2026
eb6f6f3
into
refresh/laravel-13-api-toolbox
7 checks passed
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
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.
Stacked on #2; GitHub retargets it to
mainwhen #2 merges.composer auditonly knows published advisories, so a freshly compromised release passes it, and the daily bot would open a PR for it. Laravel Vet (beta, v0.2.1) closes that gap.What it does
vet.jsontrust file. It records the version and file hash of each of the 150 packages.composer installfails on anything not recorded, including a version re-published with different files.minimum-release-age: 7keeps every release younger than a week out ofcomposer update. Two exclusions:juststeveking/*, because those packages are first-party.roave/security-advisories, because it isdev-latestand re-publishes with every advisory. A hold makes it uninstallable and delays exactly what it exists to block.laravel/framework13.37.0 to 13.35.0 andguzzle8.3.0 to 8.2.0. Tests and PHPStan pass on them.The bot
composer updatewrites the lock and then exits 1, because nothing new is trusted yet. The workflow tolerates that, but still fails on a real resolution error.--no-pluginsand putsvet's list of what needs review in the PR body.GITHUB_TOKENdon't trigger other workflows, so CI doesn't run on the bot's commit. The gate takes effect when you pushvet.jsonto the bot branch after reviewing (composer install --no-plugins, then./vendor/bin/vet), and that push runs CI. If you want CI on the bot commit itself, the workflow needs a PAT or GitHub App token as a secret.Checked locally
vet.jsonfailscomposer install, and a fresh install from an emptyvendor/passes with all 150 trusted.85 tests pass;
composer lintandcomposer stanare clean.