chore(security): refresh roave/security-advisories guard to 2026-08-01 - #103
Merged
rubenvdlinde merged 1 commit intoAug 3, 2026
Merged
Conversation
…-> 2026-08-01) The lockfile pinned roave/security-advisories to a commit from 2026-03-20, so the metapackage's conflict rules — and therefore the protection against installing known-vulnerable dependency versions — were frozen at that date. Refreshed to the 2026-08-01 tip. composer audit --locked: clean before and after.
Contributor
Quality Report — ConductionNL/openbuild @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| composer | ✅ | ✅ 100/100 | |||
| npm | ✅ | ✅ 662/662 | |||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | ⏭️ |
Coverage: 89.4% (17/19 statements)
Quality workflow — 2026-08-03 09:29 UTC
Download the full PDF report from the workflow artifacts.
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
1 participant
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.
What
Refreshes the
roave/security-advisoriesguard incomposer.lock.Why
roave/security-advisoriesis a metapackage whose only job is to conflict withknown-vulnerable package versions, so Composer refuses to install them.
composer.jsondeclares it as
dev-latest— butcomposer.lockpins a specific commit, andcomposer install(which is exactly what theSecurity (composer)CI job runs) honoursthat pin. The pinned commit here was months old, which means the conflict rules — and
therefore all protection against CVEs published since that date — were frozen.
This is not theoretical. Refreshing the same stale pin elsewhere in the fleet today
surfaced live advisories that the old guard silently permitted:
softwarecatalog— 9 advisories onguzzlehttp/guzzle7.10.0 /guzzlehttp/psr7,including CVE-2026-55568 (HTTPS proxy silently downgraded to cleartext).
nextcloud-app-templateandpetstore— 6 Twig sandbox-escape advisories ontwig/twigv3.26.0. The stale guard's rule stopped attwig/twig <3.19.Verification
composer audit --lockedrun before and after this change.historical lockfiles and correctly reported their advisories (softwarecatalog pre-fix lock
→ 9, nextcloud-app-template pre-fix lock → 6, petstore
main→ 6). A clean result from acommand that cannot fail would be worthless; this one demonstrably can fail.
Diff scope
composer.lockonly.