@bobbykim/mcl-carousel
carousel component 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 11 approved packages and no malicious indicators; dormancy appears to be genuine inactivity, not takeover. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 3 / 6 | |
| 0.9.5 | 3 / 6 | |
| 0.9.4 | 3 / 6 | |
| 0.9.3 | 3 / 6 | |
| 0.9.2 | 3 / 6 | |
| 0.9.1 | 3 / 6 | |
| 0.9.0 | 3 / 6 | |
| 0.8.3 | 3 / 6 |
v0.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bobbykim.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.