Merged
Conversation
Contributor
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 18 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Review Summary by QodoAdd Dependabot lockfile fixer workflow for npm
WalkthroughsDescription• Add dedicated GitHub Actions workflow for auto-repairing Dependabot lockfiles • Workflow runs on Dependabot PRs with same-repo guard and narrow scope • Uses Node 24 and oleg-koval/dependabot-lockfile-fixer action • Update README maintenance notes about automatic lockfile refresh Diagramflowchart LR
A["Dependabot PR opened/updated"] -->|triggers| B["dependabot-lockfile-fixer workflow"]
B -->|checks| C["Same-repo & dependabot[bot] actor"]
C -->|if valid| D["Checkout PR branch"]
D --> E["Setup Node.js 24"]
E --> F["Run lockfile fixer"]
F -->|commits| G["Auto-repair package-lock.json"]
File Changes1. .github/workflows/dependabot-lockfile-fixer.yml
|
Code Review by Qodo
1. Write token executes PR code
|
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 4, 2026
## [1.7.1](v1.7.0...v1.7.1) (2026-04-04) ### ⚙️ Continuous Integrations * **dependabot:** add lockfile fixer workflow ([#59](#59)) ([287745b](287745b))
|
🎉 This PR is included in version 1.7.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
Comment on lines
+3
to
+45
| on: | ||
| pull_request_target: | ||
| types: | ||
| - opened | ||
| - reopened | ||
| - synchronize | ||
| - ready_for_review | ||
|
|
||
| permissions: | ||
| contents: write | ||
| pull-requests: write | ||
|
|
||
| concurrency: | ||
| group: dependabot-lockfile-fixer-${{ github.event.pull_request.number }} | ||
| cancel-in-progress: true | ||
|
|
||
| jobs: | ||
| fix-lockfiles: | ||
| if: > | ||
| github.actor == 'dependabot[bot]' && | ||
| github.event.pull_request.head.repo.full_name == github.repository | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: Checkout PR branch | ||
| uses: actions/checkout@v4 | ||
| with: | ||
| ref: ${{ github.event.pull_request.head.ref }} | ||
| repository: ${{ github.event.pull_request.head.repo.full_name }} | ||
| fetch-depth: 0 | ||
| token: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| - name: Setup Node.js | ||
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: 24 | ||
|
|
||
| - name: Fix lockfiles | ||
| uses: oleg-koval/dependabot-lockfile-fixer@v1 | ||
| with: | ||
| github_token: ${{ secrets.GITHUB_TOKEN }} | ||
| package_manager: npm | ||
| working_directory: . |
There was a problem hiding this comment.
1. Write token executes pr code 🐞 Bug ⛨ Security
The new workflow runs on pull_request_target with contents: write, checks out the PR branch, and then runs an npm-based lockfile fixer, meaning PR-controlled code paths (npm lifecycle scripts) can execute with a write-scoped GITHUB_TOKEN. This can be abused to perform unintended repository writes using that token.
Agent Prompt
### Issue description
`pull_request_target` workflows run with elevated permissions. This workflow checks out PR code and then runs an npm-based lockfile regeneration step while holding a write-scoped `GITHUB_TOKEN`, enabling PR-controlled execution paths (npm lifecycle scripts) to run with repository write access.
### Issue Context
You want to safely refresh lockfiles for same-repo Dependabot PRs without allowing PR-controlled code execution to access a write token.
### Fix Focus Areas
- .github/workflows/dependabot-lockfile-fixer.yml[3-45]
- package.json[59-68]
### Suggested remediation options
1) **Prefer `pull_request` over `pull_request_target`** if it still provides sufficient permissions for same-repo Dependabot branches in your repo.
2) If you must keep `pull_request_target`, **avoid running install scripts** during lockfile regeneration by replacing the third-party action with explicit commands that disable scripts, e.g.:
- `npm ci --ignore-scripts` (or equivalent)
- `npm install --package-lock-only --ignore-scripts`
Then commit/push only `package-lock.json`.
3) **Use a tightly-scoped token** (GitHub App token / fine-grained PAT limited to pushing to the Dependabot PR branch) instead of a broadly-privileged default token.
4) **Minimize permissions** to only what is required to push the lockfile commit (typically `contents: write` only).
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
Comment on lines
+40
to
+43
| - name: Fix lockfiles | ||
| uses: oleg-koval/dependabot-lockfile-fixer@v1 | ||
| with: | ||
| github_token: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
2. Action not pinned 🐞 Bug ⛨ Security
The workflow uses oleg-koval/dependabot-lockfile-fixer@v1, which is a mutable tag, while running with repository write permissions. If that tag is retargeted upstream, arbitrary code would execute in this repo with contents: write.
Agent Prompt
### Issue description
Using `uses: <owner>/<repo>@v1` is mutable and can change over time. With write permissions, this becomes a supply-chain risk.
### Issue Context
This workflow has `contents: write` and passes `GITHUB_TOKEN` into the action.
### Fix Focus Areas
- .github/workflows/dependabot-lockfile-fixer.yml[11-13]
- .github/workflows/dependabot-lockfile-fixer.yml[40-45]
### How to fix
- Replace `olek-koval/dependabot-lockfile-fixer@v1` with a **pinned commit SHA** (optionally keep the tag in a comment for readability), e.g.:
- `uses: oleg-koval/dependabot-lockfile-fixer@<full_sha>`
- (Optional) Add a periodic dependency update process for action SHAs so upgrades are intentional and reviewed.
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
oleg-koval
added a commit
that referenced
this pull request
Apr 4, 2026
* ci(dependabot): add lockfile fixer workflow (#59) * release(version): Release 1.7.1 [skip ci] ## [1.7.1](v1.7.0...v1.7.1) (2026-04-04) ### ⚙️ Continuous Integrations * **dependabot:** add lockfile fixer workflow ([#59](#59)) ([287745b](287745b)) * docs(readme): refresh badges and branch guidance (#58) * release(version): Release 1.7.2 [skip ci] ## [1.7.2](v1.7.1...v1.7.2) (2026-04-04) ### 📚 Documentation * **readme:** refresh badges and branch guidance ([#58](#58)) ([5b82595](5b82595)) * fix(ci): run lockfile fixer for reopened dependabot prs * fix(ci): run lockfile fixer for reopened dependabot prs * ci(dependabot): auto-merge safe npm updates * docs(release): clarify branch migration and defaults * release(version): Release 1.7.3 [skip ci] ## [1.7.3](v1.7.2...v1.7.3) (2026-04-04) ### 🐛 Bug Fixes * **ci:** run lockfile fixer for reopened dependabot prs ([cea37bf](cea37bf)) --------- Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
oleg-koval
added a commit
that referenced
this pull request
Apr 4, 2026
…dates (#61) * ci(dependabot): add lockfile fixer workflow (#59) * release(version): Release 1.7.1 [skip ci] ## [1.7.1](v1.7.0...v1.7.1) (2026-04-04) ### ⚙️ Continuous Integrations * **dependabot:** add lockfile fixer workflow ([#59](#59)) ([287745b](287745b)) * docs(readme): refresh badges and branch guidance (#58) * release(version): Release 1.7.2 [skip ci] ## [1.7.2](v1.7.1...v1.7.2) (2026-04-04) ### 📚 Documentation * **readme:** refresh badges and branch guidance ([#58](#58)) ([5b82595](5b82595)) * fix(ci): run lockfile fixer for reopened dependabot prs * fix(ci): run lockfile fixer for reopened dependabot prs * ci(dependabot): auto-merge safe npm updates * docs(release): clarify branch migration and defaults * release(version): Release 1.7.3 [skip ci] ## [1.7.3](v1.7.2...v1.7.3) (2026-04-04) ### 🐛 Bug Fixes * **ci:** run lockfile fixer for reopened dependabot prs ([cea37bf](cea37bf)) * chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates Bumps the npm_and_yarn group with 3 updates in the / directory: [braces](https://github.com/micromatch/braces), [lodash](https://github.com/lodash/lodash) and [picomatch](https://github.com/micromatch/picomatch). Updates `braces` from 3.0.2 to 3.0.3 - [Changelog](https://github.com/micromatch/braces/blob/master/CHANGELOG.md) - [Commits](micromatch/braces@3.0.2...3.0.3) Updates `lodash` from 4.17.21 to 4.18.1 - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](lodash/lodash@4.17.21...4.18.1) Updates `picomatch` from 2.3.0 to 2.3.2 - [Release notes](https://github.com/micromatch/picomatch/releases) - [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md) - [Commits](micromatch/picomatch@2.3.0...2.3.2) --- updated-dependencies: - dependency-name: braces dependency-version: 3.0.3 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: lodash dependency-version: 4.18.1 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: picomatch dependency-version: 2.3.2 dependency-type: indirect dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: oleg koval <5700359+oleg-koval@users.noreply.github.com> Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
Summary
Add a dedicated workflow to auto-repair stale
package-lock.jsonfiles on same-repo Dependabot PRs.Problem
This repository releases from CI and commits
package-lock.json, so Dependabot PRs can drift behindmainand fail with lockfile-only conflicts.Solution
Run
oleg-koval/dependabot-lockfile-fixeron Dependabot pull requests with a narrowpull_request_targetworkflow and same-repo guard.Changes
.github/workflows/dependabot-lockfile-fixer.ymldependabot[bot]and same-repo PR branchespackage_manager: npmmastertomainmigrationOut of scope
Related issues
None
Validation
npm run docs:index:checkScreenshots / Demo
N/A
Risk and impact
Low. The workflow only runs for same-repo Dependabot PRs and only writes back to that PR branch.
Breaking changes
None
Documentation
Updated
readme.mdmaintenance notes.Reviewer notes
This is intentionally isolated from the regular CI and release workflows so the fix path stays limited to Dependabot lockfile drift.