@bobbykim/mcl-cards
card components based on @bobbykim/manguito-theme
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 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.9.3 | 2 / 7 | |
| 0.9.2 | 2 / 7 | |
| 0.9.1 | 2 / 7 | |
| 0.9.0 | 2 / 7 | |
| 0.8.5 | 2 / 7 | |
| 0.8.4 | 2 / 7 | |
| 0.8.3 | 2 / 7 | |
| 0.8.2 | 2 / 7 | |
| 0.8.1 | 2 / 7 | |
| 0.8.0 | 2 / 7 | |
| 0.7.5 | 2 / 7 | |
| 0.7.4 | 2 / 7 | |
| 0.7.3 | 2 / 7 | |
| 0.7.2 | 2 / 7 |
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.