@opentripplanner/location-field
A component for display and finding a location
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@tanstack/react-pacer | AI (phantom-deps): Declared dep used indirectly via config/re-export pattern in OTP-UI monorepo; stable false positive. | ai | |
| phantom-deps | phantom-dep:@conveyal/geocoder-arcgis-geojson | AI (phantom-deps): Declared dep used indirectly via config/re-export pattern in OTP-UI monorepo; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.1.7 | 8 / 1 | |
| 4.1.6 | 8 / 1 | |
| 4.1.1 | 8 / 1 | |
| 4.1.0 | 7 / 1 | |
| 4.0.4 | 7 / 2 | |
| 4.0.3 | 7 / 2 | |
| 4.0.2 | 7 / 2 | |
| 4.0.1 | 7 / 2 |
v4.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.1
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.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.