@freightos/fusion-location-input
Fusion Location 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:yalc | AI (dependencies): yalc is a local package publishing tool used only in dev scripts; not a runtime risk. | ai | |
| dependencies | unvetted-dep:peer-deps-externals-webpack-plugin | AI (dependencies): Build-time webpack plugin; no runtime exposure in published output. | ai | |
| phantom-deps | phantom-dep:yup | AI (phantom-deps): Validation library likely used in build/test config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:yalc | AI (phantom-deps): yalc is a dev publishing tool referenced in scripts/config only, not a runtime import. | ai | |
| phantom-deps | phantom-dep:axios-mock-adapter | AI (phantom-deps): Test mock adapter; referenced in test config, not a runtime import. | ai | |
| phantom-deps | phantom-dep:formik | AI (phantom-deps): Form library referenced in config/test context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:peer-deps-externals-webpack-plugin | AI (phantom-deps): Build-time webpack plugin; referenced in config, not imported at runtime. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.6 | 5 / 5 | |
| 2.2.1 | 5 / 4 | |
| 2.2.0 | 5 / 4 | |
| 2.1.1 | 5 / 4 | |
| 1.1.1 | 5 / 4 | |
| 1.0.1 | 5 / 4 |
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.