Repository navigation
Comparing changes
Open a pull request
base repository: juliangruber/brace-expansion
base: v5.0.7
head repository: juliangruber/brace-expansion
compare: v5.0.9
- 15 commits
- 6 files changed
- 3 contributors
Commits on Jul 1, 2026
-
Bump @sigstore/core from 3.1.0 to 3.2.1 (#117)
Bumps [@sigstore/core](https://github.com/sigstore/sigstore-js) from 3.1.0 to 3.2.1. - [Release notes](https://github.com/sigstore/sigstore-js/releases) - [Commits](https://github.com/sigstore/sigstore-js/compare/[email protected]...@sigstore/[email protected]) --- updated-dependencies: - dependency-name: "@sigstore/core" dependency-version: 3.2.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for b3bfbf0 - Browse repository at this point
Copy the full SHA b3bfbf0View commit details
Commits on Jul 2, 2026
-
Bump @sigstore/verify from 3.1.0 to 3.1.1 (#118)
Bumps [@sigstore/verify](https://github.com/sigstore/sigstore-js) from 3.1.0 to 3.1.1. - [Release notes](https://github.com/sigstore/sigstore-js/releases) - [Commits](https://github.com/sigstore/sigstore-js/compare/[email protected]...@sigstore/[email protected]) --- updated-dependencies: - dependency-name: "@sigstore/verify" dependency-version: 3.1.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 69bd65a - Browse repository at this point
Copy the full SHA 69bd65aView commit details -
Bump sigstore from 4.1.0 to 4.1.1 (#119)
Bumps [sigstore](https://github.com/sigstore/sigstore-js) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/sigstore/sigstore-js/releases) - [Commits](https://github.com/sigstore/sigstore-js/compare/[email protected]@4.1.1) --- updated-dependencies: - dependency-name: sigstore dependency-version: 4.1.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 43122df - Browse repository at this point
Copy the full SHA 43122dfView commit details -
Bump markdown-it from 14.1.0 to 14.2.0 (#113)
Bumps [markdown-it](https://github.com/markdown-it/markdown-it) from 14.1.0 to 14.2.0. - [Changelog](https://github.com/markdown-it/markdown-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/markdown-it@14.1.0...14.2.0) --- updated-dependencies: - dependency-name: markdown-it dependency-version: 14.2.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 8cb5716 - Browse repository at this point
Copy the full SHA 8cb5716View commit details
Commits on Jul 15, 2026
-
Remove Node.js 18 support (#110)
* Remove Node.js 18 support * update lockfile
Configuration menu - View commit details
-
Copy full SHA for 5bf809e - Browse repository at this point
Copy the full SHA 5bf809eView commit details -
Bump ws from 8.19.0 to 8.21.1 (#124)
Bumps [ws](https://github.com/websockets/ws) from 8.19.0 to 8.21.1. - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@8.19.0...8.21.1) --- updated-dependencies: - dependency-name: ws dependency-version: 8.21.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for e729ba6 - Browse repository at this point
Copy the full SHA e729ba6View commit details
Commits on Jul 21, 2026
-
Bump brace-expansion from 2.0.2 to 2.1.2 (#126)
Bumps [brace-expansion](https://github.com/juliangruber/brace-expansion) from 2.0.2 to 2.1.2. - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](v2.0.2...v2.1.2) --- updated-dependencies: - dependency-name: brace-expansion dependency-version: 2.1.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for bd14690 - Browse repository at this point
Copy the full SHA bd14690View commit details -
Bump tar from 7.5.16 to 7.5.20 (#127)
Bumps [tar](https://github.com/isaacs/node-tar) from 7.5.16 to 7.5.20. - [Release notes](https://github.com/isaacs/node-tar/releases) - [Changelog](https://github.com/isaacs/node-tar/blob/main/CHANGELOG.md) - [Commits](isaacs/node-tar@v7.5.16...v7.5.20) --- updated-dependencies: - dependency-name: tar dependency-version: 7.5.20 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 592a36f - Browse repository at this point
Copy the full SHA 592a36fView commit details
Commits on Jul 23, 2026
-
* fix: bound total expansion length to prevent OOM crash (CVE-2026-14257) The max option caps the number of expansions but not their length, so chaining many brace groups (e.g. '{a,b}'.repeat(1500)) keeps the count under max while each result grows with the number of groups. Building 100k long results, plus the intermediate arrays combined along the way, exhausted memory and crashed the process with an uncatchable OOM error. Add an EXPANSION_MAX_LENGTH cap (configurable via a maxLength option) that bounds the total characters accumulated while expanding, so output is truncated instead of growing without bound. * fix: expand tail iteratively to bound memory and stack depth (CVE-2026-14257) Address advisory review feedback. Thread a single accumulator through the whole expand() call rather than capping length per recursion level, so total memory stays bounded by maxLength instead of groups * maxLength. Expand the post tail iteratively instead of recursing once per brace group, so deeply chained input (previously ~2,700+ groups) no longer overflows the stack. Both are achieved by folding over the top-level brace groups left to right with a running accumulator.
Configuration menu - View commit details
-
Copy full SHA for a1bd339 - Browse repository at this point
Copy the full SHA a1bd339View commit details -
Configuration menu - View commit details
-
Copy full SHA for 96a63c0 - Browse repository at this point
Copy the full SHA 96a63c0View commit details
Commits on Jul 24, 2026
-
Bump linkify-it from 5.0.1 to 5.0.2 (#128)
Bumps [linkify-it](https://github.com/markdown-it/linkify-it) from 5.0.1 to 5.0.2. - [Changelog](https://github.com/markdown-it/linkify-it/blob/master/CHANGELOG.md) - [Commits](markdown-it/linkify-it@5.0.1...5.0.2) --- updated-dependencies: - dependency-name: linkify-it dependency-version: 5.0.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 473d3e9 - Browse repository at this point
Copy the full SHA 473d3e9View commit details
Commits on Jul 27, 2026
-
docs: make the maxLength example produce a non-empty result (#137)
* docs: make the maxLength example produce a non-empty result * Update README.md --------- Co-authored-by: Julian Gruber <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c66e5f9 - Browse repository at this point
Copy the full SHA c66e5f9View commit details
Commits on Jul 30, 2026
-
* Bound total expansion length across comma alternatives `maxLength` was enforced in `combine`, the one place output grows, but not on the `values` array built to feed it. Each alternative in `{a,b,c,...}` is expanded by its own `expand_` call, so each received a full independent `maxLength` allowance, and the results were concatenated with no running total. With `A` alternatives, `values` could reach `A * maxLength` characters before `combine` ever got the chance to truncate it. A ~25 KB input with 400 alternatives grew `values` past the heap limit and crashed the process with an uncatchable out-of-memory error, bypassing the mitigation added in 5.0.8 for CVE-2026-14257. Track the running result count and character length while appending alternatives, and stop once either bound is reached. * Apply maxLength while generating sequences `expandSequence` was bounded by `max`, the result count, but never consulted `maxLength`. A padded element's width follows the input, so a wide pad made it generate `max` wide elements only for `combine` to discard nearly all of them. Memory stays flat here, since V8 represents those padded strings as cons-strings, which is likely why this path was not caught alongside the memory-exhaustion issue. The cost is time instead, proportional to `max * width`: a ~400 KB input blocked the event loop for over two minutes. Pass `maxLength` into the generation loop and stop once the sequence's own characters reach it. Output is byte-identical; only the discarded work is removed. The same input now returns in ~18 ms. * fix: don't count dropped empties against `max` Capping the intermediate `values` array at `max` entries counted alternatives that `combine` goes on to drop as empty, so `max` stopped bounding the number of *kept* results: `expand('{a,,b}', { max: 2 })` returned `['a']` where it used to return `['a', 'b']`. Skip those values rather than counting them. The cap itself stays - it is what bounds the array when the values are empty and so contribute no characters for `maxLength` to see.Configuration menu - View commit details
-
Copy full SHA for 688a99e - Browse repository at this point
Copy the full SHA 688a99eView commit details -
test: cover dropping empties when only some prefixes are empty
The pre-filter added in 688a99e only skips empty alternatives when every accumulated prefix is still empty. Once an earlier group has put a non-empty string into `acc`, that filter switches off and `combine`'s own empty-result check is the only thing dropping the empties the remaining empty prefixes produce. Nothing exercised that path, so branch coverage sat at 98.91% and `npm test` exited 1 on tap's coverage gate even though all tests passed. Cover it with `{a,}{,}` and friends, which bash expands to `a a`.
Configuration menu - View commit details
-
Copy full SHA for f6f3939 - Browse repository at this point
Copy the full SHA f6f3939View commit details -
1
Configuration menu - View commit details
-
Copy full SHA for fbcf8ec - Browse repository at this point
Copy the full SHA fbcf8ecView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v5.0.7...v5.0.9