@alfalab/core-components-switch
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing description/repo/keywords is a stable pattern across the @alfalab family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Chronic pattern for @alfalab monorepo component packages; not indicative of malice. | ai | |
| provenance | no-provenance | AI (provenance): No provenance has been a stable characteristic of this package family across all versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 6.1.3 | 6 / 0 | |
| 6.1.2 | 6 / 0 | |
| 6.1.1 | 6 / 0 | |
| 6.1.0 | 6 / 0 | |
| 6.0.3 | 5 / 0 | |
| 6.0.2 | 5 / 0 | |
| 6.0.1 | 5 / 0 | |
| 6.0.0 | 5 / 0 |
v6.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.