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 (pinned via overrides)
Update type: security (patch, via override)
Why now
Security advisory GHSA-7w5x-hrqm-74c2: smol-toml Denial of Service via malformed TOML documents (stack overflow via unrestricted recursion), affecting versions <=1.7.0. npm audit reports 2 high-severity findings. No newer markdownlint-cli2 release is available yet that bundles a fixed smol-toml, so an npm overrides pin is used.
Risk assessment
Runtime/dev/build/CI scope: dev-only (markdownlint-cli2 is a devDependency used for linting)
Reachability: lockfile-only for the root package; not imported by application runtime source. docs-site/package-lock.json already resolves smol-toml to 1.8.0 independently and needs no change.
Result: npm audit high-severity findings went from 2 → 0. Diff is exactly the 1-line override addition in package.json plus the corresponding single lockfile entry update (version/resolved/integrity) for node_modules/smol-toml. Both files verified as valid JSON.
Remaining gaps: full npm install with lifecycle scripts was not exercised in this sandbox (pre-existing environment limitation with the default internal registry mirror); resolution was validated via --package-lock-only --ignore-scripts against the public npm registry, which is sufficient to confirm the dependency tree and audit outcome.
Registry preflight: repo's default .npmrc points at an internal Azure DevOps feed mirror (unreachable/403 in this sandbox); resolved instead against https://registry.npmjs.org/ directly, an existing documented limitation unrelated to this change
Why this manifest set is atomic
Only the root package.json/package-lock.json pair is touched; they share one lockfile and one resolver invocation.
docs-site has its own independent package-lock.json and already resolves the fixed version — excluded because it needs no change.
No other manifests reference smol-toml.
Breaking changes
None. smol-toml 1.7.0 → 1.8.0 is a minor bump with no known breaking changes for this dev-only linting dependency.
Sensitive surface area
None (dev-only, linting tool dependency; no auth/crypto/payment/database/CI-runtime code paths).
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 (both package.json and package-lock.json must be reverted together).
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
smol-tomlDenial of Service via malformed TOML documents (stack overflow via unrestricted recursion), affecting versions<=1.7.0.npm auditreports 2 high-severity findings. No newermarkdownlint-cli2release is available yet that bundles a fixedsmol-toml, so an npmoverridespin is used.Risk assessment
markdownlint-cli2is a devDependency used for linting)markdownlint-cli2)docs-site/package-lock.jsonalready resolvessmol-tomlto1.8.0independently and needs no change.Validation
npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts,npm audit --registry=https://registry.npmjs.org/ --jsonnpm audithigh-severity findings went from 2 → 0. Diff is exactly the 1-line override addition inpackage.jsonplus the corresponding single lockfile entry update (version/resolved/integrity) fornode_modules/smol-toml. Both files verified as valid JSON.npm installwith lifecycle scripts was not exercised in this sandbox (pre-existing environment limitation with the default internal registry mirror); resolution was validated via--package-lock-only --ignore-scriptsagainst the public npm registry, which is sufficient to confirm the dependency tree and audit outcome.Toolchain / registry preflight
v22.23.2, npm10.9.8(repo requires Node>=20.19.0, compatible).npmrcpoints at an internal Azure DevOps feed mirror (unreachable/403 in this sandbox); resolved instead againsthttps://registry.npmjs.org/directly, an existing documented limitation unrelated to this changeWhy this manifest set is atomic
package.json/package-lock.jsonpair is touched; they share one lockfile and one resolver invocation.docs-sitehas its own independentpackage-lock.jsonand already resolves the fixed version — excluded because it needs no change.smol-toml.Breaking changes
smol-toml1.7.0 → 1.8.0 is a minor bump with no known breaking changes for this dev-only linting dependency.Sensitive surface area
Smart-Dependabot-Merge-Candidate: yes
Reviewer checklist
Rollback guidance
package.jsonandpackage-lock.jsonmust be reverted together).Control Plane
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
Add this agentic workflow to your repo
To install this agentic workflow, run