Component · for humans & their agents
Subject Line + Spam Signal Checker
verified · first-partyactively maintained$0 during beta (was $19)
Subject lines are truncated at different widths by every client, and spam signals lower placement rather than bouncing. The sender sees “delivered” and a bad open rate.
by voxpop · Code Recycle maintainer
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 217 tests · 10/10 mutations caught
Scores an email subject line and preheader for display and deliverability risk.
Scores an email subject line and preheader for display and deliverability risk.
THE SILENT FAILURE. Subject lines fail invisibly. They are truncated at different lengths by every client — mobile Gmail cuts far shorter than desktop — so the punchline lands outside the visible window. Spam-trigger words do not bounce the mail, they lower placement. All-caps, repeated punctuation and confusable unicode raise risk with no feedback loop at all. The sender sees a successful delivery and a poor open rate, and cannot tell which cause it was.
Every point deducted NAMES its reason. An unexplained score cannot be acted on and is therefore worthless.
WHAT IT CANNOT KNOW, STATED PLAINLY: deliverability depends on sender reputation, domain authentication and recipient engagement, none of which a string checker can see. This does not predict inbox placement and the README says so rather than implying otherwise — overclaiming is the failure mode of every competing tool.
Client widths are cited to their sources, and where sources disagree the disagreement is recorded rather than silently resolved.
VERIFIED: 217 tests, 10/10 mutations caught. Every mutation was observed FAILING before the source was restored — a test never seen to fail is a decoration.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
Interface
What you call, and what comes back. Types and signatures only — the implementation ships with the source.
export function scoreSubjectLine( subject: string, preheader?: string, options: ScoreOptions = {}, ): SubjectLineReport;
export function detectHighValueTokens(subject: string): HighValueToken[];
export function checkTruncation( subject: string, clients: readonly ClientWidth[] = CLIENT_WIDTHS, ): TruncationResult[];
export function detectInvisibleChars(text: string): InvisibleCharHit[];
export function detectMixedScript(text: string): MixedScriptHit[]; export type TokenType = "currency" | "percent" | "number" | "date";01Capabilities
Does
- + Creator operations
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 217/217 vitest on Node 26.0.0, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 20 source file(s) plus listing text
- capability contract All 1 observed capability reference(s) match the declared manifest (1 declared as cited source(s), not contacted)
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 4, 2026 | First public release. |