@opentabs-dev/opentabs-plugin-prescript-test
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): Early-stage org package; no provenance is consistent with the rest of the opentabs-dev ecosystem at this stage. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Package has a meaningful description in its opentabs metadata block; the missing npm-level description field is a minor gap, not a malware signal, and stable for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.6 | 1 / 5 | |
| 0.0.5 | 1 / 5 | |
| 0.0.4 | 1 / 5 | |
| 0.0.3 | 1 / 5 | |
| 0.0.2 | 1 / 5 | |
| 0.0.1 | 1 / 5 |
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
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.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.