# Upstream origin and triage

- Original package: `regex-parser@2.3.1`
- Repository: https://github.com/IonicaBizau/regex-parser.js
- Source commit: https://github.com/IonicaBizau/regex-parser.js/commit/455a3b0e259b4b970e331ae9d41663718b2ae34e
- Source directory: `.`
- npm tarball: https://registry.npmjs.org/regex-parser/-/regex-parser-2.3.1.tgz
- SHA512 integrity: `sha512-yXLRqatcCuKtVHsWrNg0JL3l1zGfdXeEvDa0bdu4tCDQw0RpMDZsqbkyRTUnKMR0tXF627V2oEWjBEaEdqTwtQ==`
- npm last-release age selects maintenance scope; it does not imply no ongoing source development.

## Reviewed issues

Primary-source snapshot: `2026-09-29T00:21:42.769891+00:00`. Most recently updated 100 open and 30 closed issue/PR entries; PRs removed. This is triage evidence, not a claim of exhaustive review.

Maintenance adoption with preserved runtime payload. No runtime defect correction is claimed. Reports remain visible for subsequent targeted reproduction.


The structured snapshot in `.stackline/issue-triage.json` also records recently closed reports. Issues for unrelated packages in shared monorepositories were qualified as outside this fork’s runtime scope. No maintainer was contacted.

Parse delimiter/flag boundaries in linear work while preserving upstream semantics across 5,000 generated differential inputs. User-selected regular expressions retain their original semantics.