@explorins/pers-signer
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
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.0.34 | 0 / 10 | |
| 1.0.33 | 0 / 10 | |
| 1.0.32 | 0 / 10 | |
| 1.0.31 | 0 / 10 | |
| 1.0.27 | 0 / 10 | |
| 1.0.26 | 0 / 10 | |
| 1.0.25 | 0 / 10 | |
| 1.0.18 | 0 / 10 | |
| 1.0.17 | 0 / 10 | |
| 1.0.16 | 0 / 10 | |
| 1.0.12 | 0 / 10 | |
| 1.0.11 | 0 / 10 | |
| 1.0.9 | 0 / 10 | |
| 1.0.8 | 0 / 10 | |
| 1.0.6 | 0 / 10 | |
| 1.0.5 | 0 / 10 |
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.