Security audit
Security checks for vulnerabilities and agentic risk
This skill adds or migrates app email through a clearly disclosed workflow with test-only checks, reversible changes, and user control over production updates.
Mailfully will process your app's outgoing email. Keep test credentials locally and review changes before enabling live sending. Opens and clicks are tracked by default, including rewritten sign-in links; disable tracking if unsuitable. Use a locked local script runner where possible. Before sharing suppression lists, confirm the support channel and an approved transfer method. CLI login stores a credential beyond this session.
Referenced artifact was not completely inspected
ils with `ERR_PACKAGE_PATH_NOT_EXPORTED`. Use the TypeScript `fetch` helper in `references/rest-clients.md`. If this machine's Node is older than 24, skip the C
Referenced artifact was not completely inspected
| None | new integration | `references/api-essentials.md`, then `references/rest-clients.md` unless the project is Node 24 or later |
Referenced artifact was not completely inspected
`references/rest-clients.md` (Java, C#, Elixir and others): port the TypeScript `fetch` helper,
Referenced artifact was not completely inspected
- **Node older than 24, or CommonJS (TypeScript or JavaScript):** the `fetch` helper in `references/rest-clients.md`. No package to install.
Referenced artifact was not completely inspected
- **Python, Ruby, Go, PHP:** that language's helper in `references/rest-clients.md`.
Referenced artifact was not completely inspected
- **Django or Rails:** add the adapter in `references/rest-clients.md` (a Django email backend, a
Referenced artifact was not completely inspected
- `references/rest-clients.md`: not Node 24 or later. Helpers per language, Django and Rails adapters.
Referenced artifact was not completely inspected
| `resend` | migration | `references/migrate-resend.md` |
Referenced artifact was not completely inspected
- `references/migrate-resend.md`: from Resend (React Email, attachments by URL, scheduled sends).
Referenced artifact was not completely inspected
| `@sendgrid/mail`, `sendgrid` | migration | `references/migrate-sendgrid.md` |
Referenced artifact was not completely inspected
`references/migrate-sendgrid.md`. It waits out `retry-after` and prefixes every `Idempotency-Key` with
Referenced artifact was not completely inspected
- `references/migrate-sendgrid.md`: from SendGrid, and `sendEach` for any per-recipient send.
Referenced artifact was not completely inspected
| `postmark` | migration | `references/migrate-postmark.md` |
Referenced artifact was not completely inspected
- `references/migrate-postmark.md`: from Postmark (message streams, tracking flags, templates).
Referenced artifact was not completely inspected
`, Symfony `MAILER_DSN`, or Django, Rails or Laravel set to SMTP | migration | `references/migrate-nodemailer.md` (a `MAILER_DSN` naming SendGrid or Postmark us
Referenced artifact was not completely inspected
- `references/migrate-nodemailer.md`: from Nodemailer, `smtplib` or any framework's SMTP settings.
Referenced artifact was not completely inspected
Read `references/webhooks.md`.
Referenced artifact was not completely inspected
- `references/webhooks.md`: phase 5. Event names, headers, tested verifiers, the test vector.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
import os
ENV_FILE = ".env" # the env file the app loads
def load_mailfully_key(path=ENV_FILE):
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
Ground rules for every phase:
- Never ask the user to paste the key into the chat. Never read, print, grep or parse the env file or the key in shell.
If a key shows up in the conversation anyway, tell the user to revoke it and create a new one.
- The user pastes secrets into the env file themselves; the one exception is the key from the browser
sign-in in phase 2, which the CLI writes. You never write a key: the only thing you write about
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
Test mode needs no DNS and no verified domain, and it delivers to no real inbox.
4. Prints the returned `id` (`messageId` from the Nodemailer wrapper) and `status`. If the send returns
`status: "canceled"`, or raises on it (`MailfullySendError` with `type: "canceled"` from the wrapper, or the Django or Rails adapter's error), every recipient was suppressed: say so and stop; do not report success.
5. Polls `GET https://api.mailfully.com/v1/emails/<id>` with the same key (header
`Authorization: Bearer <key>`, read from the environment inside the script) every 5 s for up to 2
minutes, printing `last_event` each time. It keeps polling on `queued`, `sending`, `sent`, `held`,
`paused_hold` or `released`, stops on `delivered` (success), and stops on any other word as final and
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
After (with send_email from the Python helper in rest-clients.md):
# send_email (mailfully_client.py, from rest-clients.md) POSTs to https://api.mailfully.com/v1/emails.
import logging
from mailfully_client import send_email
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
After (with send_email from the Python helper in rest-clients.md):
# send_email (mailfully_client.py, from rest-clients.md) POSTs to https://api.mailfully.com/v1/emails.
import logging
from mailfully_client import send_email
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
imports:
// sendEmail (lib/mailfully.ts, from rest-clients.md) POSTs to https://api.mailfully.com/v1/emails.
import { setTimeout as sleep } from "node:timers/promises";
import { MailfullyApiError, sendEmail, type MailfullyEmail } from "./mailfully";
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
# send_email and MailfullyError (mailfully_client.py, from rest-clients.md) POST to
# https://api.mailfully.com/v1/emails, take an idempotency key and carry a 429's retry-after seconds.
import http.client
import os
import time
No suspicious patterns detected.