@atlasauth/embed@0.5.0
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected runtime callers connect authentication requests to widget flows and user actions. Telemetry uses the configured frontend API and contains device and interaction measurements; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json points to the module entry and contains no install lifecycle hook.
- Authentication and sign-up flows send telemetry using the widget's configured frontend API and publishable key.
- The telemetry payload contains device metadata and a behavior recorder snapshot; the inspected recorder comment says it captures counts and timings, not field content.
- The inspected flagged callers connect passkey, form, OAuth, SSO, reset, and sign-up paths to user actions or authentication flow handling.
Source & flagged code
8 flaggedBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/embed.jsView on unpkg · L1A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/widget/social.js#virtual:normalized:round1View on unpkgFindings
Affected versions and remediation
This report applies to @atlasauth/embed@0.5.0.
See all versions of @atlasauth/embed for other recorded verdicts.
- Review the evidence and your use of @atlasauth/embed@0.5.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.