Development dependency security
Tracked by pm-r61juc and pm-fnx3np, with independent advisory evidence in pm-eqxjzl and MCP/Vite remediation in pm-5sgx37.
Development tools execute during tests, benchmarks and release preparation. Their dependencies have the same admission requirement as production packages: no known advisory may pass the required static gate unless an exact, time-bounded waiver records it (see Time-bounded advisory waivers). Run:
pnpm install --frozen-lockfile
pnpm quality:dependencies
This collects the full pnpm audit --json, with no production-only or severity
filter, and queries every npm name/version in the pnpm v9 lockfile against
OSV querybatch. The inventory
includes development, optional and platform-specific packages. Either source's
positive result blocks, even when the other returns zero. Unsupported resolutions,
empty inventories, malformed or partial responses, pagination and network failures
also block. Collection has bounded batch sizes, deadlines and no automatic retries.
Only public npm names and versions are sent to OSV.
The ignored local .cache/dependency-security/receipt.json records input hashes,
complete per-package OSV coverage, feed retrieval times, registry counts and
advisory IDs. Collection invalidates the prior receipt before querying. Database
update times are explicitly unknown: fresh retrieval does not prove a feed is
current. The SDK-owned repository-static-quality assurance gate composes a
repository-quality/dependency-advisories provider that verifies this receipt
without network access. It rejects evidence older than fifteen minutes, changed
manifests or lockfiles, incomplete coverage and unavailable sources. Fresh evidence
is required again on each CI/static or release run. Static checks refresh collection
immediately before SDK assurance evaluation, which verifies advisory evidence
before slower providers. The blocking registry command settles before OSV starts
its network deadlines.
CI retains this single receipt after successful and failed static jobs, with a
separate artifact name for each run attempt and seven-day retention. Inspect both
feeds before diagnosing a blocked collector: a positive advisory is a refusal,
even when the other feed is clean. A refusal reached after both feeds completed
names its cause, for example
Independent source reports vulnerable dependencies: <package>@<version> <advisory id>,
built only from validated lockfile and advisory fields. A collection failure
keeps the generic message and never echoes upstream text.
Time-bounded advisory waivers
An advisory that has no patched release cannot be fixed by a lockfile change,
yet the gate refuses every branch and the scheduled release until one exists.
pm-03q389 adds the only exception the
gate accepts: a recorded waiver in config/dependency-advisory-waivers.json.
{
"version": 1,
"waiver_notice_days": 3,
"waivers": [
{
"advisory": "GHSA-xxxx-xxxx-xxxx",
"package": "example-package",
"versions": ["1.2.3"],
"owner": "pm-xxxxxx",
"reason": "Why no fix can be taken yet, how the advisory reaches pm, and when it was re-verified.",
"expires_at": "2026-12-01T00:00:00Z"
}
]
}
- A waiver covers one GitHub advisory id, one npm package and its listed
exact locked versions. A report is covered only when all three match one
waiver, so a different version, package or advisory id (including
MAL-malware ids and CVE aliases) still blocks. - Both feeds are judged: OSV rows by advisory id, package and version, and
registry advisories by their
github_advisory_id,module_nameand every finding version. A registry advisory with a missing or malformed detail can never be waived. Receipt version 2 records those validated fields. pnpm counts one per advisory, not per vulnerable version, so the verifier requires each severity's count to equal the number of listed advisories with that severity. A waived advisory therefore cannot stand in for an unlisted one, and an advisory of unknown severity refuses. - The expiry is an RFC 3339 UTC instant at most 30 days past the run that judges it. Renew a waiver only after re-verifying it, and record that verification on the owner. The owner is a pm item id and the reason must be at least 20 characters.
- A waiver never covers a package that the published artifact installs. That
graph is projected from
package.jsonandpnpm-lock.yamlwith the same function that writesruntime-dependencies.json, so a stale ledger cannot hide a runtime package. Consumers audit that graph themselves and cannot rely on this repository's exception (pm-gh1748), so the fix for a runtime package is to remove it from the runtime graph. - A malformed file, waiver or notice window, a duplicate, an expired waiver, one that reaches past 30 days and one that covers a runtime package all refuse the gate, even when nothing needs the waiver. An absent file declares no waivers.
- A passing verdict lists every applied waiver under
waivedwith the feeds it covered, and every waiver that matched nothing underunused_waivers, so a retired advisory's waiver is visible before it expires.
The scheduled Waiver notice window step (defect-evidence-gate.mjs --waiver-notice) judges the same file without network access. It fails
while a waiver is inside waiver_notice_days of its expiry, on any finding
above, and when a waiver's owner is no longer an open tracker item. Closing
the owner therefore requires retiring the waiver too. See
Waiver Notice Window.
Unpatched picomatch extglob ReDoS
pm-03q389 tracks
GHSA-fc5q-39xc-vjpf
(npm advisory 1247710, high: picomatch through 4.0.7 backtracks
exponentially on single-branch repeated extglobs such as +(*)). GitHub
widened the advisory on 2026-11-17 to cover 4.0.7, the latest release, with
no patched version, and both feeds reported it on the next run, so Gates
(static) failed on every branch, main included. pm reaches picomatch through
tinyglobby, which expands the linked-artifact globs the local caller
supplies, and through fdir and Vite in development tooling. A crafted
pattern can therefore stall only the caller's own process.
pm-gh1748 removes the runtime path:
--add-glob now uses a built-in, linear-time matcher (src/core/fs/file-glob.ts)
and tinyglobby moved to the development dependencies. A consumer's
npm audit --omit=dev therefore no longer reports picomatch through pm.
Development tooling still resolves picomatch through tinyglobby (repository
scripts and the parity test), fdir and Vite. The waiver
covers picomatch 4.0.7 until 2026-12-01 with a three-day notice window.
Replace it with the patched release once upstream publishes one (fix pull
requests opened on 2026-11-17) and satisfies the dependency cooldown, then
delete the waiver and its mirrored .trivyignore entry
(CVE-2026-112366) in the same pull request; the waiver spec fails while a
.trivyignore entry has no declared waiver to mirror.
The command then verifies the installed CodSpeed bundle policy. Network/audit errors,
missing packages, incomplete policy entries, changed package files, and unreviewed
upgrades all fail. quality:static includes this command, so the existing CI,
nightly quality and release paths enforce it. The registry-owned local
preflight also requires the static gate and permits no skip. Trivy separately
includes development dependencies in its required repository scan.
Composite action refs and their executed tool versions need separate review.
pm-38w3ii pins TruffleHog's action
commit and explicitly selects scanner version 3.98.0; the action otherwise
defaults to the latest image. The workflow contract checks both values on
every TruffleHog step. Recheck the action's executable selectors when renewing
its commit pin.
Vitest mocker advisory pair
pm-vitest4112 coordinates the
manual-registration finding and
Windows redirect finding.
GHSA-qxg6-89mg-rqv8
and GHSA-xp26-3454-mjgp
affect the previously locked @vitest/mocker 4.1.11. The compatible Vitest and
coverage-provider pair now requires 4.1.12, whose shared mock-source generator
serializes module URLs and export names, including asynchronous rebinding, and
whose public redirect handler normalizes backslashes before the file allowlist
check. Both fixes apply to public mocker/interceptor WebSocket handlers. The
repository's Node test configurations do not register these handlers, so the
affected development dependency does not establish an exploitable CLI or SDK
route.
The retained hosted OSV receipt identified both advisories while the registry
audit returned zero. Keep full-lock admission mandatory and verify the patched
graph against both feeds. That patch kept Vitest 4 because CodSpeed 5.7.1 did not
accept Vitest 5. pm-fokyhh (repository-only tracker record excluded from npm) later adopted
the Vitest 5.0.5 pair with CodSpeed 6.1.0; @vitest/mocker 5.0.3 and later carry
both fixes, and the Vite 7 override is unchanged. The
installed-handler regressions run in coverage and the required native Windows
cohort, whose aggregate refuses failed, canceled or skipped partitions. The
October 15 patch releases meet pnpm's one-day minimum age on October 21 without
an exclusion. Dependabot's seven-day scheduling cooldown is unchanged.
Indexed source-map offsets
pm-dba47 tracks Dependabot alert 47 and
the new source-map cause of Scorecard alert 29.
GHSA-68fv-2mgg-jv7q
affects source-map-js before 1.2.2. Unchecked indexed-map section offsets can
block the event loop. The dependency is used by the development lint and test
graph through @eslint/css-tree, magicast and postcss; this inventory does
not establish a production exploit. The pnpm override requires a patched 1.x
release while retaining normal release-age policy and frozen installation.
The pinned pnpm 11 uses its default one-day minimum release age; the separate
seven-day Dependabot cooldown governs version-update scheduling. This repair
adds no age override or exclusion.
A clean audit feed is only evidence about that feed at its observation time. GitHub and OSV reported this advisory while the npm audit response was still empty. A freshly updated Trivy database also admitted both vulnerable and patched temporary fixtures, so that scan did not establish regression sensitivity. The independent safe constructor control rejected an oversized indexed-map offset only on the patched version, without serializing the huge offset. Read the actual locked graph and every available scanner report before claiming that findings are retired. Native scans of merged main must confirm retirement independently of green PR workflow jobs.
Worker diagnostics
pm-cql43 tracks CodeQL alert 43 in the test worker bridge. Its captured scanner flow contains a generated temporary path, so it does not prove a credential leak. The debug path nevertheless previously broadcast arbitrary CLI arguments and stderr. Debug failures now emit only a fixed notification; the complete captured result remains available to deliberate assertions. A real worker regression uses synthetic private input and verifies both notification privacy and preserved result contents, plus silence when debugging is disabled or the command succeeds. The harness is excluded from the published package.
File matching dependency removal
GHSA-vfj7-8cjw-p6xm
affects braces 3.0.3, previously reachable through the production fast-glob
dependency. A pattern under 10,000 characters can exhaust the recursive brace
expansion stack. No fixed version was published when this change was verified.
The SDK and repository censuses now use tinyglobby 0.2.17, removing fast-glob,
micromatch and braces from the installed graph. Explicit
expandDirectories: false retains file-only semantics: a directory argument
does not silently become a recursive match. Dot files, brace and extglob
patterns, absolute paths and invocation-relative anchoring remain supported.
The regression uses a real temporary directory and the same deeply nested input
that failed before the replacement. Audit errors remain mandatory failures.
Redirect credential and glob amplification advisories
pm-irviv0 tracks
GHSA-mrwp-f3q8-3g9p
(follow-redirects 1.16.0 through 1.16.1: cross-realm sensitiveHeaders
arrays are discarded, so custom credentials can follow redirects) and
GHSA-g3hv-75wg-m249
(minimatch before 11.0.1: denial of service through glob-part
amplification). Both were published on October 30 and the registry feed
reported them from the next run on main while OSV was still clean, so the
advisory gate refused every PR and the scheduled release path until the lock
changed. follow-redirects is reached only through the CodSpeed benchmark
plugin's Axios client, and minimatch through ESLint and its config array
and as a direct dependency of @stryker-mutator/core (mutation testing); all
of these are development dependencies and none establishes a CLI or SDK
route. The pnpm overrides require follow-redirects 1.16.2 or a newer
1.x release and minimatch 11.0.1 or a newer 11.x release. minimatch 11
keeps dual CommonJS and ES module exports, so ESLint's require path is
unchanged and the full lint run passes; the override applies to the Stryker
path as well. Both releases satisfy pnpm's one-day
minimum release age without an exclusion; the seven-day Dependabot cooldown
is unchanged. The gate's catch-all refusal said that no feed success could be
inferred, which hid the real cause (a non-empty registry id list); read
.cache/dependency-security/receipt.json before treating that message as a
feed outage.
CodSpeed 6.1.0 patch
CodSpeed's declared dependency previously resolved Axios 1.19.0, and both
@codspeed/core bundles embedded Axios 1.4.0. Updating the declared dependency
alone leaves those embedded implementations and their source-map contents
intact. The pnpm override selects Axios 1.20.0 or a newer compatible 1.x
release that satisfies the normal dependency cooldown. The exact-version
patch in the patch file replaces the
embedded dependency section in both CJS and ESM entries with imports of the
declared axios and form-data packages. Each entry creates its own Axios
client and retains the cancellation constructor, preserving isolation from
application request and response interceptors.
The replacement boundary starts at function bind$2(fn, thisArg) and ends
immediately before var __defProp$3 = Object.defineProperty. Only axios and
FormData$2 from that section are referenced by the retained code. The patch
preserves the preceding and following benchmark code, declarations, export
surface and native binaries. Each entry removes 19,201 embedded lines. Its map
retains 5,293 mappings, removes 39,536 obsolete mappings, and reduces its source
inventory from 131 to 21. The 6.1.0 port keeps the same boundary; upstream added
four Node-version warning exports, so the runtime suite pins 30 exports. Remaining generated positions are shifted by the
replacement's line delta; their original source, line, column and names are
preserved. Removed Axios, redirects, proxy and form-data sources are absent.
Both maps end with a newline; the integrity policy records the installed bytes.
The integrity policy pins all twelve
package-owned files by SHA-256: both entries, both maps, all three native binaries,
the manifest, declarations and declaration map, license and README. Owned
artifacts must be regular files; symlinks cannot redirect their module resolution
to an unreviewed dependency tree even when their target bytes have the same hash. Admission
also checks the exact installed file inventory, so an added executable, map or
native payload fails even when the previously approved files are unchanged.
Package-local dependency overrides also fail inventory admission: an added
node_modules/axios could shadow the audited dependency resolved by the bundle.
Only the three node-gyp-build commands and their CMD/PowerShell variants may
appear directly in node_modules/.bin. Each must be a regular file whose complete
program matches the reviewed shim templates, with
targets and module paths derived from the audited installed dependency. Arbitrary
names, nested payloads, links, altered programs and forged target markers fail;
these shims are outside the twelve package-owned hashes but are independently
validated. pm-rnpmtp renews the installer
to pnpm 11.28.5 and its bundled bins/cmd-shim generator. Separate complete shell
templates describe POSIX and Windows installations; only the host's template is
accepted. Windows shells pass Windows NODE_PATH values to native Node, and
Cygwin targets use Windows paths. CMD and PowerShell programs retain their
complete comparisons. Template changes require renewed real installation and
dependency-resolution evidence on POSIX, Git Bash and Cygwin, plus CMD and
PowerShell. The Windows script cohort downloads the archived Cygwin setup 2.937
installer and verifies its pinned SHA-512 before execution. To renew it, select
an eligible version from the official setup archive,
verify the executable against the archive's sha512.sum, and update the
versioned URL, pinned digest and workflow contract together. Preserve setup's
default package-signature verification and repeat native launcher acceptance.
Literal percent paths are exercised in disposable launcher fixtures;
the audited CodSpeed installation still refuses shell interpolation paths.
The CMD suffix follows the installed PATHEXT spelling, including .CMD;
format lookup folds its case while validating the complete program. All three
shell launchers are required, together with the CMD and PowerShell sets on
Windows. Any additional format must also contain all three commands. Missing
or duplicate launchers fail admission. Installation roots and rendered paths
containing shell interpolation syntax fail before template comparison;
ordinary paths containing spaces remain supported. Templates are comparison
data: the checker never rewrites pnpm-generated launchers.
The locked dependency graph is checked by the full audit. An
upstream upgrade requires a reviewed patch removal or refresh, renewed runtime
compatibility evidence, and a matching policy update. Never update hashes
merely to admit an unexplained difference.
Verification and scope
The admission suite edits real temporary package copies and proves that each changed package file and additional unreviewed payload is refused. The runtime integration suite uses both public entries in fresh processes, calls a real loopback HTTP server, and verifies setup, benchmark start/stop, HTTP failure conversion, exports, measurement conversions, root-frame wrappers and isolation from real application interceptors. The server observes the audited Axios transport rather than a mocked client. The existing CodSpeed workflow continues to execute the native benchmark integration.
These findings establish vulnerable dependency inventory, not a demonstrated production exploit. CodSpeed is a development dependency. Its Mongo instrumentation transport requires an explicitly configured instrumentation server; ordinary benchmarks do not configure one. Native Scorecard analysis of the merged commit must confirm alert retirement independently of local audits and PR checks.
Aus docs/DEVELOPMENT_DEPENDENCY_SECURITY.md in pm 2026.11.19. Auf GitHub ansehen