You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm audit reports a high-severity Denial of Service advisory
(GHSA-7w5x-hrqm-74c2) affecting smol-toml <=1.7.0 via malformed TOML documents. markdownlint-cli2@0.23.2 (the latest
release) still pins the vulnerable smol-toml@1.7.0; no newer markdownlint-cli2 release
exists yet that bumps it. An npm overrides entry forces the patched 1.8.0 release without
downgrading markdownlint-cli2 (the only available "fix" per npm audit is a major
downgrade to 0.21.0, which is worse).
Risk assessment
Runtime/dev/build/CI scope: dev-only (markdownlint-cli2 is a devDependency used for npm run lint:md); no production runtime path.
Reachability: smol-toml has zero own dependencies; only used internally by markdownlint-cli2 to parse its own TOML config, if any. No direct imports of smol-toml
found in this repo's source.
Validation
Commands run:
npm audit --registry=https://registry.npmjs.org/ --package-lock-only --json (before): 1 high
(smol-toml/markdownlint-cli2).
npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts
to regenerate the lockfile with the override applied.
Verified valid JSON (python3 json.load) and a minimal diff (only the single node_modules/smol-toml lockfile entry changed: version/resolved/integrity).
Remaining gaps: npm ci/full lifecycle-script install could not be run in this sandbox
(the repo's .npmrc points at an internal Azure DevOps npm mirror ms-feed-25.pkgs.visualstudio.com that returns 403 here); validated instead via --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts, which is
sufficient to prove correct resolution and the audit outcome. CI should confirm a full
install succeeds against the real internal registry.
Deployment/canary owner confirms runtime health, if needed
Rollback guidance
Revert this PR (remove the smol-toml override) or pin smol-toml back to 1.7.0 if an
incompatibility surfaces. package.json and package-lock.json must be reverted together.
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Caution
Protected files were modified in this change.
This pull request is in
request-reviewmode and requires explicit human scrutiny before merge.Protected files:
package-lock.json,package.jsonDependency Release Train Summary
What changed
package.json,package-lock.jsonsmol-toml@1.7.0(transitive, viamarkdownlint-cli2@0.23.2)smol-toml@1.8.0(pinned viaoverrides)Why now
npm auditreports a high-severity Denial of Service advisory(GHSA-7w5x-hrqm-74c2) affecting
smol-toml <=1.7.0via malformed TOML documents.markdownlint-cli2@0.23.2(the latestrelease) still pins the vulnerable
smol-toml@1.7.0; no newermarkdownlint-cli2releaseexists yet that bumps it. An npm
overridesentry forces the patched1.8.0release withoutdowngrading
markdownlint-cli2(the only available "fix" pernpm auditis a majordowngrade to
0.21.0, which is worse).Risk assessment
markdownlint-cli2is a devDependency used fornpm run lint:md); no production runtime path.markdownlint-cli2->smol-toml).smol-tomlhas zero own dependencies; only used internally bymarkdownlint-cli2to parse its own TOML config, if any. No direct imports ofsmol-tomlfound in this repo's source.
Validation
npm audit --registry=https://registry.npmjs.org/ --package-lock-only --json(before): 1 high(
smol-toml/markdownlint-cli2).npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scriptsto regenerate the lockfile with the override applied.
npm audit --registry=https://registry.npmjs.org/ --package-lock-only --json(after):0 vulnerabilities.
python3 json.load) and a minimal diff (only the singlenode_modules/smol-tomllockfile entry changed: version/resolved/integrity).npm ci/full lifecycle-script install could not be run in this sandbox(the repo's
.npmrcpoints at an internal Azure DevOps npm mirrorms-feed-25.pkgs.visualstudio.comthat returns 403 here); validated instead via--registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts, which issufficient to prove correct resolution and the audit outcome. CI should confirm a full
install succeeds against the real internal registry.
Control Plane
Reviewer checklist
Rollback guidance
smol-tomloverride) or pinsmol-tomlback to1.7.0if anincompatibility surfaces.
package.jsonandpackage-lock.jsonmust be reverted together.Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.Create the pull request manually
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Add this agentic workflow to your repo
To install this agentic workflow, run