safe-regex2
detect possibly catastrophic, exponential-time regular expressions
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Fastify ecosystem package with clear GitHub repo; lack of Sigstore provenance is common and not a meaningful risk for this well-established package. | ai | |
| dependencies | unvetted-dep:ret | AI (dependencies): ret is the canonical regex tokenizer dependency for safe-regex-style packages; its use here is expected and stable across all versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 1 / 4 | |
| 5.1.0 | 1 / 4 | |
| 5.0.0 | 1 / 6 | |
| 4.0.1 | 1 / 6 | |
| 4.0.0 | 1 / 5 | |
| 3.1.0 | 1 / 3 | |
| 3.0.0 | 1 / 2 | |
| 2.0.0 | 1 / 2 |
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.