fiftyone.geolocation@4.5.100
Perform reverse geocoding using longitude and latitude to populate postal addresses
AI Security Review
scanned 17h ago · by lpm-firewall-aiThe package's default pipeline includes runtime usage sharing that can transmit unfiltered request evidence to a 51Degrees endpoint, so this is a telemetry disclosure concern. The flagged remote-response eval finding is a false positive: the test only checks async syntax support.
Decision evidence
public snapshot- The pipeline builder enables ShareUsage by default when creating a pipeline.
- The usage-sharing code reads values from the pipeline's request evidence.
- With no cookie, query whitelist, or header blacklist configured, the usage filter shares all evidence keys.
- Usage data is sent by POST to the default 51Degrees endpoint, devices-v4.51degrees.com/new.ashx.
- The flagged eval only checks whether the runtime supports async functions; it does not execute remote response content.
- The package has no install lifecycle scripts, and its main entry only exports the geolocation modules.
- The package's stated purpose is reverse geocoding through 51Degrees services, and usage sharing is an explicit builder option.
Source & flagged code
4 flaggedSource passes code obtained from a remote response into a dynamic execution sink.
tests/geoLocationCloud.test.jsView on unpkg · L9Package source references dynamic code evaluation.
tests/geoLocationCloud.test.jsView on unpkg · L65Package source references dynamic require/import behavior.
tests/geoLocationCloud.test.jsView on unpkg · L22Findings
Affected versions and remediation
This report applies to fiftyone.geolocation@4.5.100.
See all versions of fiftyone.geolocation for other recorded verdicts.
- Review the evidence and your use of fiftyone.geolocation@4.5.100 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.