@faable/auth-js@2.21.0
<p align="center"> <a href="https://faable.com"> <img src="https://www.faable.com/assets/logo/Emblem.png" height="96"> <h3 align="center">Faable</h3> </a> </p>
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe entry points and package metadata match an authentication SDK, with no install hooks or fixed unrelated network destination identified. Requests use the configured auth domain, and token handling and session refresh match the stated purpose.
Decision evidence
public snapshot- Package metadata exposes the main and Next.js authentication library entry points, marks the package side-effect-free, and declares no lifecycle scripts.
- The client normalizes the caller-provided domain and uses it as the issuer, rather than selecting a fixed unrelated host.
- Authorization headers are built from tokens supplied to the request helper, consistent with normal authenticated API calls.
- The README describes OAuth, passwordless login, token refresh, and browser storage as the package’s purpose.
- The library handles access tokens and persists authentication state in browser storage, which is expected for an authentication client.
- Creating a client initializes session handling; this behavior is part of the documented authentication flow.
Source & flagged code
4 flaggedPackage metadata exposes the main and Next.js authentication library entry points, marks the package side-effect-free, and declares no lifecycle scripts.
package.jsonView on unpkg · L1Authorization headers are built from tokens supplied to the request helper, consistent with normal authenticated API calls.
dist/main.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @faable/auth-js@2.21.0.
See all versions of @faable/auth-js for other recorded verdicts.
- Review the evidence and your use of @faable/auth-js@2.21.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.