@salutejs/plasma-tokens-web
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 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.74.0 | 0 / 8 | |
| 1.73.0 | 0 / 8 | |
| 1.72.0 | 0 / 8 | |
| 1.71.0 | 0 / 8 | |
| 1.70.0 | 0 / 8 | |
| 1.69.0 | 0 / 8 | |
| 1.68.0 | 0 / 8 | |
| 1.67.0 | 0 / 8 | |
| 1.65.0 | 0 / 8 | |
| 1.64.0 | 0 / 8 | |
| 1.63.0 | 0 / 8 | |
| 1.62.0 | 0 / 8 | |
| 1.61.0 | 0 / 8 | |
| 1.60.0 | 0 / 8 | |
| 1.59.0 | 0 / 9 | |
| 1.58.0 | 0 / 9 | |
| 1.57.0 | 0 / 9 | |
| 1.56.0 | 0 / 9 |
v1.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.