Hi! We consume psychds-validator (currently 1.5.1) as a runtime dependency of @jspsych/metadata-cli, and Dependabot flags 11 open advisories against the exactly-pinned "undici": "5.28.4" in your package.json. Because the pin is exact, downstream projects can't remediate via their own dependency resolution (npm overrides against an exact pin corrupt tree resolution in our testing, and wouldn't protect transitive consumers anyway) — a new psychds-validator release is the only clean fix.
Advisories affecting 5.28.4 (none have a patched 5.x except the first two):
Ask: bump the dependency to "undici": "^6.27.0" (or newer). The 5→6 API is compatible for fetch/request-style usage; the highest-severity items are WebSocket-specific, so if the validator only uses undici for HTTP schema fetching, practical exposure is low — but consumers' security scanners flag it regardless, and the exact pin blocks any downstream workaround.
A caret range (rather than another exact pin) would also let consumers pick up future undici patch releases without a new validator release. Happy to open a PR with the bump if that helps — thanks for maintaining the validator!
🤖 Generated with Claude Code on behalf of @jodeleeuw
Hi! We consume
psychds-validator(currently 1.5.1) as a runtime dependency of@jspsych/metadata-cli, and Dependabot flags 11 open advisories against the exactly-pinned"undici": "5.28.4"in yourpackage.json. Because the pin is exact, downstream projects can't remediate via their own dependency resolution (npmoverridesagainst an exact pin corrupt tree resolution in our testing, and wouldn't protect transitive consumers anyway) — a newpsychds-validatorrelease is the only clean fix.Advisories affecting 5.28.4 (none have a patched 5.x except the first two):
upgradeoptionAsk: bump the dependency to
"undici": "^6.27.0"(or newer). The 5→6 API is compatible forfetch/request-style usage; the highest-severity items are WebSocket-specific, so if the validator only uses undici for HTTP schema fetching, practical exposure is low — but consumers' security scanners flag it regardless, and the exact pin blocks any downstream workaround.A caret range (rather than another exact pin) would also let consumers pick up future undici patch releases without a new validator release. Happy to open a PR with the bump if that helps — thanks for maintaining the validator!
🤖 Generated with Claude Code on behalf of @jodeleeuw