@alfalab/core-components-gallery
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): Transition from human account to org CI bot (core-ds-bot) with 643 approved packages; consistent with automation migration. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @alfalab/core-components-* packages; not a malware indicator. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-mq | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-button | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-spinner | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-tooltip | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/hooks | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-base-modal | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-typography | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-icon-button | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Automated monorepo component publish; missing metadata is expected for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-icon-view | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@alfalab/icons-glyph | AI (dependencies): Sibling package in the same @alfalab monorepo; stable false positive for this package family. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 7.1.9 | 16 / 0 | |
| 7.1.8 | 16 / 0 | |
| 7.1.7 | 16 / 0 | |
| 7.1.6 | 16 / 0 | |
| 7.1.5 | 16 / 0 | |
| 7.1.4 | 16 / 0 | |
| 7.1.3 | 16 / 0 | |
| 7.1.2 | 16 / 0 | |
| 7.1.1 | 16 / 0 | |
| 7.1.0 | 16 / 0 | |
| 7.0.6 | 16 / 0 | |
| 7.0.5 | 16 / 0 | |
| 7.0.4 | 16 / 0 | |
| 7.0.3 | 16 / 0 | |
| 7.0.2 | 16 / 0 | |
| 7.0.1 | 16 / 0 | |
| 7.0.0 | 16 / 0 | |
| 6.0.15 | 16 / 0 | |
| 6.0.14 | 16 / 0 | |
| 6.0.13 | 16 / 0 | |
| 6.0.12 | 16 / 0 | |
| 6.0.11 | 16 / 0 | |
| 6.0.10 | 16 / 0 | |
| 6.0.9 | 16 / 0 | |
| 6.0.8 | 16 / 0 | |
| 6.0.7 | 16 / 0 | |
| 6.0.6 | 16 / 0 | |
| 6.0.5 | 16 / 0 | |
| 5.12.16 | 15 / 0 | |
| 5.12.15 | 15 / 0 | |
| 5.12.14 | 15 / 0 |
v7.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.11
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.