@onefootprint/footprint-js@6.0.0
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime requests are directed to OneFootprint services for diagnostics and onboarding. The telemetry includes page and browser context on error paths, but the source does not show an unrelated recipient or an attack behavior.
Decision evidence
public snapshot- The manifest points to the inspected CommonJS bundle and lists no install lifecycle hook.
- The bundle sends SDK warnings and errors to the OneFootprint API; detailed browser context is attached to diagnostic errors.
- Onboarding uses a returned Fingerprint public key and sends the resulting visit identifiers with the onboarding authorization token to the OneFootprint API.
- The SDK can transmit the current page URL and browser characteristics in error diagnostics, but the inspected code ties that transmission to SDK warning or error paths.
Source & flagged code
5 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/footprint-js.cjsView on unpkgThe bundle sends SDK warnings and errors to the OneFootprint API; detailed browser context is attached to diagnostic errors.
dist/footprint-js.cjsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @onefootprint/footprint-js@6.0.0.
See all versions of @onefootprint/footprint-js for other recorded verdicts.
- Review the evidence and your use of @onefootprint/footprint-js@6.0.0 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.