security: clear pnpm audit findings

[0xJem]

Summary

• remediate the current moderate-or-higher pnpm audit findings
• add narrow range-scoped overrides for form-data, js-yaml, tmp, uuid, and ws
• add the exact temporary release-age exception needed for form-data@4.0.6

Validation

• pnpm audit --audit-level moderate --json
• pnpm run build
• pnpm run lint:check
• git diff --check

Summary by CodeRabbit

• Chores
  • Updated workspace dependency resolution policies to maintain consistent package versions across environments.

[coderabbitai]

Warning

Review limit reached

@0xJem, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 4 minutes and 16 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b33f9ee8-4b12-4df1-aff1-e0bbe575d1a7

📥 Commits

Reviewing files that changed from the base of the PR and between d299004 and b918931.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• pnpm-workspace.yaml

Walkthrough

pnpm-workspace.yaml is updated to add form-data@4.0.6 to the minimumReleaseAgeExclude list and to introduce or tighten conditional overrides rules for form-data, js-yaml, tmp, uuid, and ws, redirecting older version ranges to newer patch releases.

Changes

Dependency Override Policy

Layer / File(s)	Summary
Version override and exclusion rules pnpm-workspace.yaml	Adds form-data@4.0.6 to minimumReleaseAgeExclude; sets form-data@>=4.0.0 <4.0.6 → ^4.0.6; changes js-yaml override to <=4.1.1 → ^4.2.0; adds new conditional overrides for tmp@<0.2.6 → ^0.2.6, uuid@<11.1.1 → ^11.1.1, and ws@>=7.0.0 <7.5.11 → ^7.5.11.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A hop through the lock file, a tweak here and there,
Old versions of packages? Not gonna be there!
form-data and ws, uuid and tmp too,
All bumped to their freshest, shiny and new.
The rabbit approves — no stale deps in view! 🌿

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'security: clear pnpm audit findings' directly relates to the main objective of the PR, which is to address security vulnerabilities and clear pnpm audit findings through dependency overrides.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/staking-subgraph-pnpm-remediation

---

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

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm js-yaml is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/eslint@8.24.0 → npm/@graphprotocol/graph-cli@0.98.1 → npm/js-yaml@4.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report