@alfalab/core-components-tooltip
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): hextion has strong track record (623 approved, 0 rejected); transition from bot account is consistent with a CI/CD pipeline change. | ai | |
| phantom-deps | phantom-dep:@alfalab/core-components-shared | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-button | AI (dependencies): Same-org sibling component; stable pattern across all @alfalab/core-components-* packages. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-bottom-sheet | AI (dependencies): Same-org sibling component; stable pattern across all @alfalab/core-components-* packages. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-popover | AI (dependencies): Same-org sibling component; stable pattern across all @alfalab/core-components-* packages. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Same-org sibling component; stable pattern across all @alfalab/core-components-* packages. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; no provenance is consistent across all versions and poses no elevated risk here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 9.0.14 | 8 / 0 | |
| 9.0.13 | 8 / 0 | |
| 9.0.12 | 8 / 0 | |
| 9.0.11 | 8 / 0 | |
| 9.0.10 | 8 / 0 | |
| 9.0.9 | 8 / 0 | |
| 9.0.8 | 8 / 0 | |
| 9.0.7 | 8 / 0 | |
| 9.0.6 | 8 / 0 | |
| 9.0.5 | 8 / 0 | |
| 9.0.4 | 8 / 0 | |
| 9.0.3 | 8 / 0 | |
| 9.0.2 | 8 / 0 | |
| 9.0.1 | 8 / 0 | |
| 9.0.0 | 8 / 0 | |
| 8.0.14 | 7 / 0 | |
| 8.0.13 | 7 / 0 | |
| 8.0.12 | 7 / 0 | |
| 8.0.11 | 7 / 0 | |
| 8.0.10 | 7 / 0 | |
| 8.0.9 | 7 / 0 | |
| 8.0.8 | 7 / 0 | |
| 8.0.7 | 7 / 0 | |
| 8.0.6 | 7 / 0 | |
| 8.0.5 | 7 / 0 | |
| 8.0.4 | 7 / 0 | |
| 7.10.5 | 8 / 0 | |
| 7.10.4 | 8 / 0 | |
| 7.10.3 | 8 / 0 |
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.12
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.11
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.8
2 findingsThis version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.