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
Protected files were modified in this change.
This pull request is in request-review mode and requires explicit human scrutiny before merge.
Protected files: package-lock.json, package.json
Dependency Release Train Summary
What changed
Package/ecosystem: npm (root workspace)
Manifest(s): package.json, package-lock.json
Old version: smol-toml@1.7.0 (transitive, via markdownlint-cli2@0.23.2)
New version: smol-toml@1.8.0 (via added overrides.smol-toml)
Update type: security (transitive override)
Why now
GHSA-7w5x-hrqm-74c2: smol-toml denial-of-service via malformed TOML documents, affecting versions <=1.7.0. npm audit reports this as a high-severity finding against markdownlint-cli2 (root devDependency), whose only current release (0.23.2) still pins the vulnerable smol-toml@1.7.0 with no newer release available upstream.
Risk assessment
Runtime/dev/build/CI scope: dev-only (markdownlint-cli2 / lint:md script); not part of the runtime firewall/agent/proxy code paths.
Direct/transitive: transitive (forced via npm overrides).
Reachability: only reachable through the lint:md npm script (TOML config parsing for markdownlint-cli2); no application/runtime code imports smol-toml.
Validation
Commands run:
npm audit --registry=https://registry.npmjs.org/ --json (before): 2 high findings (markdownlint-cli2 via smol-toml).
npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts to regenerate the lockfile against the public registry (the repo's default private mirror is unreachable from this sandbox).
npm ci --registry=https://registry.npmjs.org/ --ignore-scripts --dry-run: clean resolution, 652 packages.
Verified package.json and package-lock.json are valid JSON.
Result: audit findings for smol-toml/markdownlint-cli2 fully resolved; lockfile diff is scoped to exactly the smol-toml entry (version/resolved/integrity) plus the 1-line overrides addition.
Remaining gaps: a full npm ci (with lifecycle scripts, against the org's default private registry mirror) could not be exercised in this sandbox (private registry mirror unreachable; full non---ignore-scripts install triggers an unrelated npm CLI crash in this sandbox environment unrelated to this change). CI should confirm a full install/build/test succeeds.
Sensitive surface area: none (dev-only lint tooling dependency, not a runtime/auth/crypto/network path).
Breaking-change notes: none; smol-toml 1.8.0 is a patch-level fix release from 1.7.0.
Risk: low
Confidence: high
Rollback steps: revert this commit (or remove the overrides.smol-toml entry and regenerate package-lock.json) to return to the prior resolved versions.
Smart-Dependabot-Merge-Candidate: yes
Reviewer checklist
CI passes
CODEOWNERS or service owners reviewed
Security-sensitive areas approved, if applicable
Deployment/canary owner confirms runtime health, if needed
Rollback guidance
Revert this PR to restore the previous smol-toml@1.7.0 resolution.
package.json and package-lock.json must be reverted together (the override and the lockfile entry are paired).
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(via addedoverrides.smol-toml)Why now
smol-tomldenial-of-service via malformed TOML documents, affecting versions<=1.7.0.npm auditreports this as a high-severity finding againstmarkdownlint-cli2(root devDependency), whose only current release (0.23.2) still pins the vulnerablesmol-toml@1.7.0with no newer release available upstream.Risk assessment
markdownlint-cli2/lint:mdscript); not part of the runtime firewall/agent/proxy code paths.overrides).lint:mdnpm script (TOML config parsing for markdownlint-cli2); no application/runtime code importssmol-toml.Validation
npm audit --registry=https://registry.npmjs.org/ --json(before): 2 high findings (markdownlint-cli2viasmol-toml).npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scriptsto regenerate the lockfile against the public registry (the repo's default private mirror is unreachable from this sandbox).npm audit --registry=https://registry.npmjs.org/ --json(after): 0 vulnerabilities.npm ci --registry=https://registry.npmjs.org/ --ignore-scripts --dry-run: clean resolution, 652 packages.package.jsonandpackage-lock.jsonare valid JSON.smol-toml/markdownlint-cli2fully resolved; lockfile diff is scoped to exactly thesmol-tomlentry (version/resolved/integrity) plus the 1-lineoverridesaddition.npm ci(with lifecycle scripts, against the org's default private registry mirror) could not be exercised in this sandbox (private registry mirror unreachable; full non---ignore-scriptsinstall triggers an unrelated npm CLI crash in this sandbox environment unrelated to this change). CI should confirm a full install/build/test succeeds.Control Plane
Sensitive surface area: none (dev-only lint tooling dependency, not a runtime/auth/crypto/network path).
Breaking-change notes: none;
smol-toml1.8.0 is a patch-level fix release from 1.7.0.Risk: low
Confidence: high
Rollback steps: revert this commit (or remove the
overrides.smol-tomlentry and regeneratepackage-lock.json) to return to the prior resolved versions.Smart-Dependabot-Merge-Candidate: yes
Reviewer checklist
Rollback guidance
smol-toml@1.7.0resolution.package.jsonandpackage-lock.jsonmust be reverted together (the override and the lockfile entry are paired).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