fix: set npm open-pull-requests-limit to 0 for security-only policy

[don-petry]

Summary

• Sets open-pull-requests-limit for the npm ecosystem from 10 to 0 in .github/dependabot.yml
• Per dependabot policy, application ecosystems should use 0 to suppress routine version-update PRs while still allowing security-alert-triggered PRs (which bypass the limit)
• The github-actions ecosystem correctly retains 10

Closes #173

Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 42 minutes and 54 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ea0c4268-ffaa-4e3e-aef6-4336cdf818c9

📥 Commits

Reviewing files that changed from the base of the PR and between 98cc446 and edfb4ee.

📒 Files selected for processing (1)

• .github/dependabot.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/issue-173-20260419-2033

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[don-petry]

@don-petry — PR is ready for review. Single-line config change: npm open-pull-requests-limit set from 10 → 0 in .github/dependabot.yml, bringing the repo into compliance with the dependabot security-only policy.

[Copilot]

Pull request overview

Updates Dependabot configuration to comply with the organization’s “security-only” policy for application ecosystems by preventing routine npm version-update PRs while still allowing security-alert PRs.

Changes:

• Set open-pull-requests-limit: 0 for the npm ecosystem in .github/dependabot.yml.
• Kept the github-actions ecosystem limit at 10 as-is.

[donpetry-bot]

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: 262a47f8a9d38274ff807f0fca0cb364cb0d8154
Review mode: triage-approved (single reviewer)

Summary

Single-line change to .github/dependabot.yml setting the npm ecosystem's open-pull-requests-limit from 10 to 0, bringing the repo into compliance with the org's dependabot security-only policy. The github-actions ecosystem correctly retains its limit of 10. Confirms the triage tier's low-risk assessment.

Linked issue analysis

Closes #173 (Compliance: wrong-limit-npm), an automated compliance-audit finding that explicitly requests open-pull-requests-limit: 0 for the npm ecosystem with a reference to the standards doc. The PR applies exactly that remediation — nothing more, nothing less. With limit 0, routine version-update PRs are suppressed while security-alert-triggered PRs still bypass the limit, matching the policy's intent.

Findings

No issues found.

• Diff is a single value change on one line; no other config keys (schedule, labels, directory, ecosystem list) were touched.
• Scope is appropriately narrow — github-actions ecosystem entry is untouched, consistent with the policy distinguishing application vs. CI ecosystems.
• PR description accurately reflects the change and cites the governing standard.
• No unresolved review threads or unanswered human-reviewer questions; Copilot reviewer left a descriptive (non-blocking) overview.

CI status

All required checks green:

• CodeQL Analyze (actions) — SUCCESS
• CodeQL Analyze (javascript-typescript) — SUCCESS
• CodeQL Analyze (python) — SUCCESS
• CodeQL (rollup) — SUCCESS
• CodeRabbit — SUCCESS
• SonarQube Cloud quality gate — passed (0 new issues)

---

Reviewed automatically by the PR-review agent (single-reviewer mode: opus 4.7). Reply if you need a human review.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud