@alfalab/core-components-input
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): Part of a large monorepo component library; missing metadata is a consistent pattern across all @alfalab/core-components-* packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across the @alfalab monorepo; not indicative of malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for this publisher's bot-published monorepo packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 17.1.7 | 10 / 0 | |
| 17.1.6 | 10 / 0 | |
| 17.1.5 | 10 / 0 | |
| 17.1.4 | 10 / 0 | |
| 17.1.3 | 10 / 0 | |
| 17.1.2 | 10 / 0 | |
| 17.1.1 | 10 / 0 | |
| 17.1.0 | 10 / 0 | |
| 17.0.1 | 10 / 0 | |
| 17.0.0 | 10 / 0 | |
| 16.1.0 | 10 / 0 | |
| 16.0.5 | 10 / 0 | |
| 16.0.4 | 10 / 0 | |
| 16.0.3 | 10 / 0 | |
| 15.7.0 | 10 / 0 |
v17.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v15.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.