@alfalab/core-components-tabs
Tabs components
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 623 approved packages; consistent with org-level publisher transition, not a takeover. | ai | |
| dependencies | unvetted-dep:@alfalab/icons-glyph | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-tag | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-badge | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-types | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/hooks | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-skeleton | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-icon-button | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-picker-button | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-keyboard-focusable | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Bot-published monorepo; no provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-shared | AI (dependencies): Sibling alfalab monorepo dep; stable pattern across all versions of this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 10.0.16 | 17 / 0 | |
| 10.0.15 | 17 / 0 | |
| 10.0.14 | 17 / 0 | |
| 10.0.13 | 17 / 0 | |
| 10.0.12 | 17 / 0 | |
| 10.0.11 | 17 / 0 | |
| 10.0.9 | 17 / 0 | |
| 10.0.8 | 17 / 0 | |
| 10.0.7 | 17 / 0 | |
| 10.0.6 | 17 / 0 | |
| 10.0.5 | 17 / 0 | |
| 10.0.4 | 17 / 0 | |
| 10.0.3 | 17 / 0 | |
| 10.0.2 | 17 / 0 | |
| 10.0.1 | 17 / 0 | |
| 10.0.0 | 17 / 0 | |
| 9.2.12 | 16 / 0 | |
| 9.2.11 | 16 / 0 | |
| 9.2.10 | 16 / 0 | |
| 9.2.9 | 16 / 0 | |
| 9.2.8 | 16 / 0 | |
| 9.2.7 | 16 / 0 | |
| 9.2.6 | 16 / 0 | |
| 9.2.5 | 16 / 0 | |
| 9.2.4 | 16 / 0 | |
| 9.2.3 | 16 / 0 | |
| 9.2.2 | 16 / 0 | |
| 9.2.1 | 16 / 0 | |
| 8.13.6 | 15 / 1 | |
| 8.13.5 | 15 / 1 | |
| 8.13.4 | 15 / 1 |
v10.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.6
2 findingsThis version was published by a different npm account than previous versions on 2025-12-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.
v9.2.5
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.
v9.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.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.
v9.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.1
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.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.5
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. 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.13.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.