postboi@0.31.0
<div align="center"> <img src="https://raw.githubusercontent.com/postboi-mail/postboi/refs/heads/main/static/logo.svg" alt="Postboi" width="250" />
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is not an npm lifecycle malware chain, but the CLI automatically uploads third-party credentials collected during BYO setup. Warn rather than block because activation requires explicit user CLI commands and the behavior is presented as team credential synchronization.
Decision evidence
public snapshot- The CLI collects provider fields marked secret, then automatically calls credential synchronization during setup.
- Credential synchronization PUTs the collected variables to the Postboi API endpoint.
- `postboi env push` reads recognized credentials from project env files and uploads them.
- The package advertises that `postboi init` pushes credentials as it collects them.
- The manifest's only lifecycle hook runs `svelte-kit sync`; it does not invoke the CLI.
- Credential collection/upload is reached through explicit CLI `init` or `env` commands, not import-time execution.
- No hidden shell payload, browser credential-store harvesting, or install-time network execution was found.
Source & flagged code
6 flaggedSource appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L108Source appears to collect browser login credentials for exfiltration.
dist/cli.jsView on unpkg · L108Findings
Affected versions and remediation
This report applies to postboi@0.31.0.
See all versions of postboi for other recorded verdicts.
- Review the evidence and your use of postboi@0.31.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.