postboi@0.43.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 2mo ago · by lpm-firewall-aiThe scanner findings arise from a mail-provider CLI that intentionally manages credentials and provider APIs. Source inspection found no install-time CLI execution, hidden collection, or unconsented outbound credential transfer.
Decision evidence
public snapshot- The package has a prepare lifecycle hook.
- The explicitly invoked env push command can read provider credential variables and send them to the configured Postboi API.
- The prepare hook only runs SvelteKit synchronization and falls back to an empty echo; it does not invoke the bundled CLI.
- The credential upload path requires the postboi env push command and a POSTBOI_TOKEN.
- CLI dispatch runs credential and project-write operations only for named user commands; there is no import-time or install-time exfiltration path.
Source & flagged code
6 flaggedSource appears to send environment or credential material to an external endpoint.
dist/cli.jsView on unpkg · L47Source appears to collect browser login credentials for exfiltration.
dist/cli.jsView on unpkg · L47Findings
Affected versions and remediation
This report applies to postboi@0.43.0.
See all versions of postboi for other recorded verdicts.
- Review the evidence and your use of postboi@0.43.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.