postboi@0.7.0
<div align="center"> <img src="https://raw.githubusercontent.com/darbymanning/postboi/refs/heads/main/static/logo.svg" alt="Postboi" width="250" />
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection shows a legitimate email library with an interactive setup CLI; the suspicious filesystem, child_process, dynamic import, env, and network usage are package-aligned and user-triggered. No install/import-time malicious behavior or unconsented data exfiltration was found.
Decision evidence
public snapshot- dist/cli.js can write user-selected env files and .gitignore during explicit `postboi init`.
- dist/cli.js can spawn host/package-manager CLIs after interactive confirmation.
- dist/config.js dynamically imports local postboi.config.* files on send path.
- package.json prepare only runs `svelte-kit sync || echo ''`; no install-time package code execution found.
- dist/cli.js actions are gated behind explicit `postboi init` and interactive prompts.
- dist/cli.js device auth calls postboi.email CLI endpoints for documented cloud login.
- dist/* provider network calls target email provider APIs and send user-supplied mail payloads.
- dist/env.js only reads .env/.env.local as local configuration fallback; no exfiltration code found.
- No persistence, destructive behavior, credential harvesting, reviewer prompt manipulation, or AI-agent control writes found.
Source & flagged code
2 flaggedPackage source references dynamic require/import behavior.
dist/config.jsView on unpkg · L76This package version adds a dangerous source file absent from the previous stored version.
dist/cli.jsView on unpkgFindings
Affected versions and remediation
This report applies to postboi@0.7.0.
See all versions of postboi for other recorded verdicts.
- Review the evidence and your use of postboi@0.7.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.