escape-delims
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:frep | AI (dependencies): frep is a jonschlinkert utility for string replacement, consistent with this package's purpose. Same trusted publisher; no threat signal. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4308 days old; provenance attestation did not exist when it was published. Not a meaningful risk signal for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 2 / 2 | |
| 0.3.0 | 1 / 4 | |
| 0.2.0 | 2 / 5 | |
| 0.1.1 | 1 / 3 | |
| 0.1.0 | 1 / 3 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.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.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.