6.9 KiB
Development dependency triage
Source: exact A3 eb2538772e1bfabbeb291e4a5efa177c79074de1, isolated branch codex/dev-dependency-triage. This is a bounded npm dependency investigation, not formal integrated security acceptance. The redirect-header qualification and committed audit receipts were read before work.
Findings and applicability
The fresh full lock-only audit returned 50 package records (7 moderate, 43 high), not the historical 49. Those records deduplicate to three concrete advisories; other records are npm metavulnerability propagation through Jest and ESLint. They are development tooling in this lock. Attacker-controlled patterns, directory trees, or tooling configuration would be needed to reach these availability failures. A production HTTP exploit, tenant impact, or data disclosure was not demonstrated. Treat tooling that processes untrusted contributions as exposed until independently assessed.
| Advisory | Concrete affected lock entries at baseline | Result |
|---|---|---|
| Picomatch repeated-extglob ReDoS, high / GHSA-fc5q-39xc-vjpf | 2.3.2 under anymatch and micromatch; root 4.0.5 | Official registry latest is 4.0.7 and advisory affects <=4.0.7 with no patched release. OPEN; upgrading to latest would not qualify a fix. |
| Minimatch globparts amplification, moderate | Root 9.0.9 and TypeScript ESLint's nested 10.2.6 | PARTIALLY REMEDIATED: nested copy becomes 11.0.9 through upstream TypeScript ESLint 8.73.0. Root 9.0.9 remains under glob/Jest; its ^9 range cannot accept patched >=11.0.1. Trigger requires optimizationLevel >=2 and attacker-controlled patterns. |
| Glob cancellation bypass, moderate | Root 10.5.0; nested 7.2.3 is outside this advisory's >=9 range | OPEN: patched >=14.0.2 does not satisfy Jest's ^10.5.0 range. Requires async traversal using cancellation and attacker-influenced patterns/trees. No forced cross-major override or Jest downgrade applied. |
The audit's suggested Jest 30.2.0, jsdom environment 29.7.0, and Next ESLint config 14.2.35 downgrades are not accepted remedies: they change the supported toolchain rather than supply compatible patched leaf packages. No audit suppression, force fix, rule weakening, production configuration, or dependency override was added.
Compatible change
npm update typescript-eslint --package-lock-only --ignore-scripts --no-audit uses eslint-config-next 16.4.6's existing typescript-eslint: ^8.56.0 range. Eleven coordinated TypeScript ESLint entries move 8.68.0 to 8.73.0; the maintainer now declares minimatch ^11.0.1, selecting nested 11.0.9. Its required @isaacs/nonrecursive-glob-match 1.1.0 is added, and the ESLint plugin's allowed ignore dependency updates 7.0.6 to 7.0.16. There are exactly 13 changed existing lock entries and one addition; see machine-readable evidence/lock-delta.json. Direct dependency declarations, application source, Jest/Next versions, and existing overrides remain unchanged. Package.json adds only the explicit Node regression command.
Minimatch 11.0.9 requires Node 20 or >=22. Verification uses the recorded local Node version; Node 18 is not qualified for this updated tool dependency. Next 16 already requires Node >=20.9.0. Install scripts were disabled without changing approval policy.
Verification and evidence limits
- Fresh isolated
npm ci --ignore-scripts --no-audit: PASS, 826 installed packages.npm lsfor the affected trees: PASS; nested installed minimatch 11.0.9 and TypeScript ESLint 8.73.0 agree with the lock. Shared A3 and sibling node_modules were not used or modified. - Bounded regression on official baseline minimatch 10.2.6 tarball: expected FAIL, missing the expansion-budget exception. Only eight repetitions (at most 256 patterns), local process, 15-second outer timeout; no abusive payload or service target.
- Permanent
npm run test:glob-security: PASS, two cases for expansion rejection and ordinary path behavior. The first exploratory assertion expected the earlier 11.0.1 cap behavior, while 11.0.9 throws RangeError; corrected to the installed source's explicit rejection behavior. That initial failed exploratory output was overwritten by the runner and is not a retained native receipt. Final test and independent baseline receipts are retained. npm run test:redirect-security: PASS, two existing same/cross-realm cases. Full frontend ESLint and TypeScript checks: PASS without configuration changes.- Candidate full lock audit: FAIL exit1, 49 records (2 moderate, 47 high), still three concrete advisories. The affected nested minimatch node is removed from its advisory; root minimatch remains. Five TypeScript ESLint metavulnerability severities change moderate to high through residual picomatch propagation; @types/jest disappears despite unchanged Jest entries. These registry/metavulnerability changes are not evidence that this patch eliminated an independent advisory or reduced aggregate risk. Native snapshots are preserved separately.
- Candidate production-tree lock audit (
--omit=dev): PASS exit0, zero returned findings. This is scoped evidence, not a full dependency or release clearance. - Own
graphify update .: PASS, AST-only, 19,837 nodes / 48,046 edges. Optional PDF/SQL extraction dependencies were absent. Newly generated untracked graph artifacts are retained in siblingdev-dependency-triage-evidence/graphify-out; shared A3 graph was not updated. - NOT RUN: full build/browser lane, Jest suite (Jest and runtime dependencies unchanged), backend, hosted CI, providers, live models, native/device/AT, formal integrated security scan, deployed or production validation. No runtime/UI/document behavior claim is made from tooling checks.
evidence/SOURCE_RECEIPTS.json binds exact source hashes, commands, versions, exits, and native gzip receipts. Raw subprocess stdout/stderr bytes avoid Windows PowerShell encoding conversion. Official registry metadata and advisory/fix sources are retained with hashes. Parent integration must rerun the narrow checks after a fresh locked install; rollback is a revert and locked reinstall, which restores the affected nested version. No push, main merge, orchestrator action, or deployment was performed.
Root recovery qualification, 18 November 2026
The isolated candidate remained source-identical to efa438201 through the usage-limit interruption. Root ran the standard Next16.4.6 build: compile, TypeScript and static export passed exit0 without warning bypass. Root also repeated the two glob and two redirect regressions, all passing; repeated cases are not added to prior test totals. Exact native outputs are gzip-bound in the receipt. No browser or formal integrated security qualification is implied. Earlier NOT RUN build statement is historical and superseded by this scoped result; Node20/Linux/hosted checks remain separate.