oparser
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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): Established package with trusted publisher; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.1.1 | 1 / 2 | |
| 3.1.0 | 1 / 2 | |
| 3.0.24 | 1 / 2 | |
| 3.0.23 | 1 / 1 | |
| 3.0.22 | 1 / 1 | |
| 3.0.21 | 1 / 1 | |
| 3.0.20 | 1 / 1 | |
| 3.0.19 | 1 / 1 | |
| 3.0.18 | 1 / 1 | |
| 3.0.17 | 1 / 1 | |
| 3.0.16 | 1 / 1 |
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.