@financial-times/o3-button
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
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.16.0 | 0 / 1 | |
| 3.15.0 | 0 / 1 | |
| 3.14.0 | 0 / 1 | |
| 3.13.1 | 0 / 1 | |
| 3.12.2 | 0 / 1 | |
| 3.12.1 | 0 / 1 | |
| 3.12.0 | 0 / 1 | |
| 3.11.0 | 0 / 1 | |
| 3.10.0 | 0 / 1 | |
| 3.9.0 | 0 / 1 | |
| 3.8.0 | 0 / 1 | |
| 3.7.0 | 0 / 1 | |
| 3.6.0 | 0 / 1 | |
| 3.5.0 | 0 / 1 | |
| 3.4.0 | 0 / 1 | |
| 3.3.2 | 0 / 1 | |
| 3.3.1 | 0 / 1 | |
| 3.3.0 | 0 / 1 | |
| 3.2.0 | 0 / 1 | |
| 3.1.0 | 0 / 1 | |
| 3.0.1 | 0 / 1 | |
| 3.0.0 | 0 / 1 |
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.