Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs(security): record the undici exact-pin rationale - #529

Merged
ndycode merged 1 commit into
mainfrom
claude/audit-14-undici-pin-docs
Jun 10, 2026
Merged

ndycode merged 1 commit into
mainfrom
claude/audit-14-undici-pin-docs

Conversation

@ndycode

@ndycode ndycode commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Summary

Documents the undici exact-pin rationale in SECURITY.md's Dependency and Release Hygiene section, in the same style as the existing hono/rollup entries — audit roadmap §4.5.5 (docs/audits/AUDIT_2026-06-10.md, PR #522).

Changes

New "Runtime dependency pin rationale" entry explaining why undici is pinned exactly to 6.25.0:

  • only runtime HTTP dependency (ProxyAgent dispatch + local-bridge fetch fallback)
  • it drives the published engines.node >=18.17.0 floor
  • dispatcher behavior is tested surface for the rotation proxy, so version movement should be a deliberate bump, never a silent range resolution
  • undici 7.x is explicitly deferred until Node 18 support is dropped (7.x raises the floor to Node 20)

Validation

  • npx vitest run test/documentation.test.ts — 25/25 (doc-integrity suite)

Risk / Rollback

Docs-only. Related: #518 (engines floor), #523 (runtime-smoke job), #528 (@types/node pin) — this completes the floor-management story.

https://claude.ai/code/session_01XNtnkLbBiXZxfQQYLMpucB


Generated by Claude Code

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Greptile Summary

docs-only change adding a undici exact-pin rationale to SECURITY.md's Dependency and Release Hygiene section, matching the existing hono/rollup style.

  • adds a new "Runtime dependency pin rationale" subsection under dependencies (distinct from the existing "Security override rationale" under overrides), explaining that undici is pinned to 6.25.0 because it is the sole runtime http dependency, it drives the engines.node >=18.17.0 floor, and its dispatcher behavior is part of the tested rotation proxy surface — with migration to 7.x deferred until node 18 support is dropped.

Confidence Score: 5/5

docs-only edit with no runtime or security surface changes — safe to merge as-is

the change is a single paragraph added to SECURITY.md; factual claims match the repo's established node floor, the undici version in package.json, and the rotation proxy test surface described in AGENTS.md. no code, no config, no token or windows-path handling touched.

no files require special attention

Important Files Changed

Filename Overview
SECURITY.md adds "Runtime dependency pin rationale" subsection for undici 6.25.0 exact pin; content is accurate, style matches existing hono/rollup entries, no code touched

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[undici 6.25.0 exact pin] --> B{why exact pin?}
    B --> C[only runtime HTTP dep\nProxyAgent + fetch fallback]
    B --> D[drives engines.node >=18.17.0 floor]
    B --> E[dispatcher behavior = tested surface\nrotation proxy]
    E --> F[version bump must be deliberate\nnot silent range resolution]
    A --> G{upgrade to 7.x?}
    G -->|blocked| H[7.x raises floor to Node 20\ndeferred until Node 18 dropped]
Loading

Reviews (1): Last reviewed commit: "docs(security): record the undici exact-..." | Re-trigger Greptile

undici is the only runtime HTTP dependency, drives the engines floor,
and its dispatcher behavior is tested surface for the rotation proxy;
the exact pin keeps version movement deliberate. Notes the undici 7.x
deferral until Node 18 support is dropped. Audit roadmap 4.5.5.

https://claude.ai/code/session_01XNtnkLbBiXZxfQQYLMpucB
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@coderabbitai

coderabbitai Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

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

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ 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.

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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 15fe699f-dfce-4fe5-984c-e20bca251565

📥 Commits

Reviewing files that changed from the base of the PR and between 98d9819 and b96714d.

📒 Files selected for processing (1)
  • SECURITY.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/audit-14-undici-pin-docs
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch claude/audit-14-undici-pin-docs

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

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

@ndycode
ndycode merged commit 8b49486 into main Jun 10, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants