@alfalab/core-components-navigation-bar-private
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): core-ds-bot is the established CI publisher for the @alfalab org; transition from hextion is a documented bot handoff. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-button | AI (dependencies): Same @alfalab monorepo; sibling dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-shared | AI (dependencies): Same @alfalab monorepo; sibling dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@alfalab/hooks | AI (dependencies): Same @alfalab monorepo; sibling dep, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-icon-button | AI (dependencies): Same @alfalab monorepo; sibling dep, not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @alfalab packages; no provenance is expected for this publisher. | ai | |
| dependencies | unvetted-dep:@alfalab/core-components-typography | AI (dependencies): Same @alfalab monorepo; sibling dep, not a third-party risk. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.0.10 | 9 / 0 | |
| 2.0.9 | 9 / 0 | |
| 2.0.8 | 9 / 0 | |
| 2.0.7 | 9 / 0 | |
| 2.0.6 | 9 / 0 | |
| 2.0.5 | 9 / 0 | |
| 2.0.4 | 9 / 0 | |
| 2.0.3 | 9 / 0 | |
| 2.0.2 | 9 / 0 | |
| 2.0.1 | 9 / 0 | |
| 2.0.0 | 9 / 0 | |
| 1.1.7 | 9 / 0 | |
| 1.1.6 | 9 / 0 | |
| 1.1.5 | 9 / 0 | |
| 1.1.4 | 9 / 0 | |
| 1.1.3 | 9 / 0 | |
| 1.1.2 | 9 / 0 | |
| 1.1.1 | 9 / 0 | |
| 1.1.0 | 9 / 0 |
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
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.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.