@alfalab/core-components-amount
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard implicit dependency of TypeScript; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; missing metadata is typical for internal scoped packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.1.1 | 4 / 0 | |
| 5.1.0 | 4 / 0 | |
| 5.0.1 | 4 / 0 | |
| 5.0.0 | 4 / 0 | |
| 4.1.0 | 4 / 0 | |
| 3.11.0 | 4 / 0 |
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.