Repository navigation
Conversation
Lockfile-only. package.json already allows it (undici ^8.10.0); this moves the locked top-level undici 8.10.0 -> 8.11.2 (advisory range 8.0.0-8.10.1) and the nested @ai-sdk/provider-utils undici 6.28.1 -> 6.29.0. npm audit --omit=dev --audit-level=moderate: exit 1 -> exit 0 (11 low remain, below the gate threshold). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Scaffold Handoff — For Your Coding Agent
Immutability CheckMode: advisory ✅ No immutable files were modified in this branch. Changed Files
Needs Adversarial Review — Do NOT Apply YetThese proposals passed the reject check but have not been approved by
Safety Boundary
Immutable files (never modify):
Scaffold files (safe to modify):
|
|
Closing as a duplicate of #256 (Codex), which carries the same top-level One difference, stated so it is not lost: this PR also moved the nested Shared blocker after #256 merges: |
What changes
package-lock.jsononly (6 lines, 2 entries;package.jsonuntouched becauseundici ^8.10.0already admits 8.11.2):undici8.10.0 -> 8.11.2 (advisory range 8.0.0-8.10.1)@ai-sdk/provider-utilsundici6.28.1 -> 6.29.0Produced with
npm update undici --package-lock-only --ignore-scripts.Why
verifyrunsnpm audit --omit=dev --audit-level=moderatefirst and fails on main today (e.g. banner PR #258, run https://github.com/HomenShum/NodeRoom/actions/runs/37674945194). Same remedy as the closed #257 (#257), without thepackage.jsonrange bump.Evidence (local, Node 22.22.2)
npm ci --ignore-scripts && npm audit --omit=dev --audit-level=moderateKnown blocker, not fixed here (why this is a draft)
After the audit step,
npm run proofs:stalenessfails:docs/eval/noderoom-fresh-user-vertical-proof.jsonis 40.8 days old (window 30d). No npm script regenerates it. Its own doc (docs/eval/NODEROOM_FRESH_USER_VERTICAL_PROOF.md) records a live run on https://noderoom.live through GitHub OAuth, a production Convex room, and a NodeAgent run on a free OpenRouter route, so a refresh needs a signed-in human session on prod. It was not hand-edited and no window, threshold or registry entry was touched. Resolving it means re-running that live proof or pulling the claim.Gate check
Codex read-only review (
codex exec -s read-only): VERDICT: APPROVED - "no gate, threshold, audit level, skip list, or expected test value was weakened"; only six lockfile fields changed (version/resolved/integrityof the two undici entries).🤖 Generated with Claude Code