ci: add dependency-review workflow#22464
Open
GirlBossRush wants to merge 1 commit into
Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #22464 +/- ##
=======================================
Coverage 93.28% 93.29%
=======================================
Files 1032 1032
Lines 60059 60059
Branches 400 400
=======================================
+ Hits 56029 56031 +2
+ Misses 4030 4028 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Adds a `QA - Dependency review` workflow that runs
`actions/dependency-review-action` on every PR targeting `main`.
This blocks PRs that introduce a *new* dependency (direct or transitive)
with a known high or critical vulnerability in GitHub's Advisory
Database. It complements rather than duplicates Dependabot: Dependabot
surfaces vulns in already-merged dependencies; dependency-review catches
them at the moment they would be introduced.
It also catches the much narrower case that motivated this PR — a
maintainer-account-hijack publishing a malicious version to npm — only
indirectly: GitHub will not have an advisory entry until the package
has been flagged. The real value here is keeping the much larger class
of "newly introduced dep happens to carry a known CVE" out of the tree.
Configured with:
- fail-on-severity: high (block on high/critical only)
- comment-summary-in-pr: on-failure (surface diff context to
reviewers when a block fires)
Pinned to v5.0.0 (a1d282b36b6f3519aa1f3fc636f609c47dddb294).
Co-authored-by: Agent <279763771+playpen-agent@users.noreply.github.com>
GirlBossRush
force-pushed
the
ci/dependency-review
branch
from
275f0e3 to
056b5cc
Compare
rissson
reviewed
May 20, 2026
Comment on lines
+6
to
+7
| # Advisory Database supports — for this repo that's npm, Go modules, | ||
| # Python (pip/uv), and GitHub Actions. |
Member
There was a problem hiding this comment.
does that also include rust dependencies?
rissson
approved these changes
May 20, 2026
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.
Summary
Adds
.github/workflows/qa-dependency-review.yml, which runsactions/dependency-review-action@v5.0.0on every PR targetingmain.Blocks PRs that introduce a new dependency (direct or transitive, any ecosystem GitHub supports — npm, Go modules, Python, GitHub Actions) with a known high or critical vulnerability.
How this fits the rest of the supply-chain hardening
dependency-reviewcatches them at the moment they would be introduced, before merge — Dependabot only sees the world after merge..npmrc:1ignore-scripts=true+ Dependabot npm cooldown.This action does not need access to the dependency graph beyond what the PR diff exposes, so the only permission it needs is
pull-requests: write(to leave the summary comment on failure) pluscontents: read.Config
fail-on-severity: high— block on high/critical only; lower-severity introductions surface in the check summary but don't gate mergecomment-summary-in-pr: on-failure— when the action blocks a PR, post a diff-style summary as a comment so the reviewer sees context, not just a red checkTest plan
QA - Dependency review / dependency-review.