@atlasauth/embed@0.4.0
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe scanner’s account-hijack hint is not supported by the inspected behavior: authentication uses the configured client API, and the reporting code sends telemetry to that same configured API. The manifest has no install hook, and no concrete attack behavior was identified.
Decision evidence
public snapshot- package.json points to the widget module and defines no install lifecycle hook.
- The widget client uses the configured frontend API for authentication requests; sign-in, reset, social, and passkey flows submit through that client.
- Passkey assertions are obtained through WebAuthn and sent to the client passkey finish route; passkey sign-in is offered through the widget UI.
- The standalone bundle sends device and interaction telemetry to the configured frontend API’s client telemetry route; sign-in and sign-up flows invoke it as best-effort telemetry.
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.4.0.
See all versions of @atlasauth/embed for other recorded verdicts.
- Review the evidence and your use of @atlasauth/embed@0.4.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.