sc-resend — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited sc-resend (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Status: boilerplate only.
sc-cf or lib/hostinger.js automatically — no manual DNS copy-paste.| Var | Purpose |
|---|---|
RESEND_API_KEY | re_... server key |
RESEND_FROM_DOMAIN | The verified sending domain |
sc-resend/
├── SKILL.md
└── scripts/
├── verify-domain.js # register + auto-create DNS records via sc-cf / hostinger
├── api-key.js # create/rotate scoped API key
├── audiences.js # CRUD audience (optional)
└── smoke-send.js # send a test email to confirmhttps://api.resend.comAuthorization: Bearer <RESEND_API_KEY>[{ name, type, value }] — feed those into the DNS module via configureDns().v=DMARC1; p=none; initially, tighten to p=quarantine once SPF/DKIM are confirmed in DNS for 24h.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.