@alfalab/core-components-with-suffix
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 | no-provenance | AI (provenance): Org-published component library; provenance absence is consistent across all versions of this package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo component; missing metadata is a known pattern for @alfalab packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @alfalab/core-components-* packages; not a malice signal. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 6.0.9 | 5 / 0 | |
| 6.0.8 | 5 / 0 | |
| 6.0.7 | 5 / 0 | |
| 6.0.6 | 5 / 0 | |
| 6.0.5 | 5 / 0 | |
| 6.0.4 | 5 / 0 | |
| 6.0.3 | 5 / 0 | |
| 6.0.2 | 5 / 0 | |
| 6.0.1 | 5 / 0 | |
| 6.0.0 | 5 / 0 | |
| 5.0.6 | 5 / 0 | |
| 5.0.5 | 5 / 0 | |
| 5.0.4 | 5 / 0 | |
| 5.0.3 | 5 / 0 | |
| 4.2.21 | 5 / 0 |
v6.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.