slaunt@0.1.18
This package contains the client-side one-sign-in OAuth handoff for Codex and Claude Code. Each native client stores its own OAuth credentials; bootstrap credentials stay in CLI memory during setup. The Desktop vault is not used for the native OAuth hando
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no lifecycle hooks, and the setup and persistence paths are reached through an explicit CLI install flow. The included native helper is opaque and ad hoc-signed, but the inspected source describes and verifies it as the enrolled Slaunt service; I found no concrete malicious behavior.
Decision evidence
public snapshot- The manifest defines CLI binaries and test scripts, with no install, preinstall, or postinstall hook.
- The CLI runs its main setup flow only when invoked directly, and accepts the explicit `install` command.
- Setup requires a Slaunt enrollment function and restricts the issuer to HTTPS, apart from loopback HTTP.
- The background helper is copied, verified, and registered as a per-user launch agent during the install flow.
- The package describes the native helper as an enrolled Slaunt service and checks its archive hash and code signature.
- The package includes an opaque, ad hoc-signed native helper that is installed persistently on macOS after setup.
Source & flagged code
7 flaggedA manifest entrypoint or package-local install chain reaches persistence behavior.
src/desktop/broker-launch-agent.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to slaunt@0.1.18.
See all versions of slaunt for other recorded verdicts.
- Review the evidence and your use of slaunt@0.1.18 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.