@flarehr/cars-calculator
Cars Calculator
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): Private internal component library; sparse metadata is expected for org-scoped packages with long publish history. | ai |
Versions (showing 7 of 608)
| Version | Deps | Published |
|---|---|---|
| 0.4.3823 | 0 / 4 | |
| 0.4.3819 | 0 / 4 | |
| 0.4.3802 | 0 / 4 | |
| 0.4.3790 | 0 / 4 | |
| 0.4.3788 | 0 / 4 | |
| 0.4.3787 | 0 / 4 | |
| 0.4.3781 | 0 / 4 |
v0.4.3823
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3819
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3802
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3790
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3788
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3781
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.