postboi@0.6.1
<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 risky primitives are tied to explicit setup and normal email-provider configuration, not hidden install/import-time behavior. I found no concrete unconsented exfiltration, persistence, destructive action, or malicious lifecycle behavior.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
User runs `postboi init` or calls library send/config APIs
Impact
Expected config/env file updates and email-provider network requests when used
Mechanism
interactive email provider configuration and provider API clients
AI rationale
Static inspection shows risky primitives are tied to explicit setup and normal email-provider configuration, not hidden install/import-time behavior. I found no concrete unconsented exfiltration, persistence, destructive action, or malicious lifecycle behavior.
Evidence
package.jsondist/cli.jsdist/config.jsdist/registry.js.env.env.local.envrc.dev.vars.gitignorepostboi.config.ts
Network endpoints12
resend.com/api-keysaccount.postmarkapp.com/serversapp.sendgrid.com/settings/api_keysapp.mailgun.com/settings/api_security/api_keysapp.brevo.com/settings/keys/apidash.cloudflare.com/profile/api-tokensapp.mailersend.com/api-tokensapp.sparkpost.com/account/api-keysmandrillapp.com/settingsapp.useplunk.com/settings/apimailtrap.io/api-tokensapp.mailpace.com
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with medium false-positive risk.
Evidence for AI clean decision
- dist/cli.js bin is an interactive init tool that writes user-entered provider secrets to local env files.
- dist/cli.js can run host CLIs and package manager install, but only after explicit interactive prompts.
- dist/config.js dynamically imports postboi.config.* from cwd/parents on send path, enabling user project config code execution by design.
Evidence against
- package.json prepare only runs svelte-kit sync; no install-time malicious hook observed.
- No import-time credential harvesting or automatic exfiltration found in inspected entrypoints.
- Network URLs are provider account/docs URLs or normal email provider APIs, aligned with package purpose.
- Secret env names are provider config fields; CLI prompts for values rather than silently stealing them.
- File writes are expected setup files: .env variants, .gitignore, and postboi.config.ts during user-invoked init.
- No persistence, destructive behavior, hidden payload, or AI-agent control-surface mutation found.
Behavioral surface
ChildProcessCrypto
Source & flagged code
2 flaggeddist/config.jsView file
76try {
L77: const { existsSync } = await import("node:fs");
L78: const path = await import("node:path");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/config.jsView on unpkg · L76dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = postboi@0.6.0
matchedIdentity = npm:cG9zdGJvaQ:0.6.0
similarity = 0.966
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version.
dist/cli.jsView on unpkgFindings
1 Critical4 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/cli.js
MediumDynamic Requiredist/config.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to postboi@0.6.1.
See all versions of postboi for other recorded verdicts.
- Review the evidence and your use of postboi@0.6.1 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.