v1.0.10
Documentation and tooling only. dist/ is byte-identical to 1.0.9; no source file
changed.
Fixed
- The quality bullet claimed "no suppression comments" while the source carries five
// Stryker disablecomments. The claim was about type suppressions and read as false to
anyone who grepped for it; it now says what is true — no@ts-ignoreand no
eslint-disable.
Security
- The OSV scan was passing because it had nothing to read. The workflow ran
osv-scannerwith noactions/checkoutstep, so it walked an empty workspace and
reported "No package sources found" and "No lockfiles found" before exiting 0. A green
check meant the scanner found no files, which is indistinguishable from finding no
vulnerabilities. With the checkout in place it scans the lockfile, which is how the next
item was found. js-yamlis patched to the fixed release (GHSA-5p4m-2wfm-xmqj, CVSS 7.5). The
override floors here already scoped it per major but admitted3.15.0and4.3.0, both
covered by the advisory; they are raised to^3.15.1and^4.3.1. It reaches this repo
only throughjest->babel-plugin-istanbul->@istanbuljs/load-nyc-config, and
dependenciesis empty, so nothing here ships it and no consumer was exposed.dist/is
unaffected.
Added
check:mutantsgate (scripts/check-mutation-directives.mjs) — validates every
// Strykercomment against the grammar Stryker's own parser accepts, rejecting a reason
written after--instead of a colon (silently dropped, and the report then shows
Ignored using a comment), a reason wrapped onto a second comment line (the report keeps
only the first fragment), and a mutator name Stryker does not know, which matches nothing
and so silences nothing. Wired into CI andprepublishOnly.docs/mutation_testing_plan.mdcarries the suppression policy now shared, word for word,
across the@bymax-one/nest-*libraries.