parenthesis
Parse parentheses from a string
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 | publisher-changed | AI (provenance): dfcreative → dy is the same maintainer (Dmitry Yv) consolidating npm accounts to match their GitHub handle. Publisher dy has strong track record (90 approved, 0 rejected). | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Small stable utility package; long gaps between publishes are normal and expected for this package. | ai | |
| provenance | no-provenance | AI (provenance): Informational only; no provenance is common for packages published before Sigstore adoption. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 0 / 1 | |
| 3.1.7 | 0 / 1 | |
| 3.1.6 | 0 / 1 | |
| 3.1.5 | 0 / 1 | |
| 3.1.4 | 0 / 1 | |
| 3.1.3 | 0 / 1 | |
| 3.1.2 | 0 / 1 | |
| 3.1.1 | 0 / 1 | |
| 3.1.0 | 0 / 1 | |
| 3.0.0 | 0 / 1 | |
| 2.0.0 | 0 / 1 | |
| 1.3.0 | 0 / 1 | |
| 1.2.4 | 0 / 1 | |
| 1.2.3 | 0 / 1 | |
| 1.2.2 | 0 / 1 | |
| 1.2.1 | 0 / 1 | |
| 1.2.0 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 |
v3.1.8
2 findingsThis version was published by a different npm account than previous versions on 2021-11-20. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.