@salutejs/plasma-tokens-b2c
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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.70.0 | 0 / 8 | |
| 0.69.0 | 0 / 8 | |
| 0.68.0 | 0 / 8 | |
| 0.67.0 | 0 / 8 | |
| 0.66.0 | 0 / 8 | |
| 0.65.0 | 0 / 8 | |
| 0.64.0 | 0 / 8 | |
| 0.63.0 | 0 / 8 | |
| 0.61.0 | 0 / 8 | |
| 0.60.0 | 0 / 8 | |
| 0.59.0 | 0 / 8 | |
| 0.58.0 | 0 / 8 | |
| 0.57.0 | 0 / 8 | |
| 0.56.0 | 0 / 8 | |
| 0.55.0 | 0 / 8 | |
| 0.54.0 | 0 / 9 | |
| 0.53.0 | 0 / 9 | |
| 0.52.0 | 0 / 9 | |
| 0.51.0 | 0 / 9 |
v0.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.