open-auther@1.2.2
Professional-grade authentication and model routing library
AI Security Review
scanned 22h ago · by lpm-firewall-aiThe refresh token recipient is operator-configurable and is not checked against the credential’s original issuer, leaving a conditional exposure risk. The default issuer is expected, and the source does not show covert redirection, so this supports a warning rather than a block.
Decision evidence
public snapshot- The CLI defaults its OAuth issuer to auth.openai.com, but also accepts an issuer from the AI_AUTHER_ISSUER environment variable or its config file.
- When a saved credential needs refreshing, the code sends its refresh token to the active issuer’s /oauth/token endpoint.
- Runtime request, credential, and model-discovery paths can invoke token refresh; the recipient is not bound to the issuer that originally issued the saved token.
- The manifest lists prepublishOnly build and verification commands, not an install hook.
- The default OAuth issuer is the expected auth.openai.com host, and the alternate issuer comes from operator-controlled configuration.
- The reviewed source does not establish a package-selected unrelated default recipient or a hidden install-time credential transfer.
Source & flagged code
5 flagged · loading sourcePackage source references child process execution.
dist/chunk-6CR3K3FL.mjsView on unpkg · L1877This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to open-auther@1.2.2.
See all versions of open-auther for other recorded verdicts.
- Review the evidence and your use of open-auther@1.2.2 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.