Kikobeats / abusive

100%

push

github

feat: tell same-inbox siblings from numbered ones, add minSiblings (#5)

* feat: tell same-inbox siblings from numbered ones, add minSiblings

A numbered address is a different inbox and can be a different person:
john1987@gmail.com is not john@gmail.com. Siblings now come in two kinds.

- Same inbox: +tag on any domain, dots on Gmail only, and gmail.com and
  googlemail.com as one inbox. findSibling searches both Gmail domains,
  own domain first. Always reported.
- Numbered: after removing . _ -, the inboxes differ by one 1-2 digit
  counter next to a letter, at the end or else the start. Years
  (john1987), interior digits, mailboxes under 3 characters and
  mailboxes without letters are never numbered.

New `minSiblings` option (integer or per-candidate function): a numbered
variant is reported only once that many distinct inboxes exist, so
derek3@ is refused after derek1@ and derek2@ while one real derek84@
gets in.

Also: `limit` now pulls exactly `limit` entries (it pulled one extra,
which could fetch an extra Stripe page) and is validated; short and
letterless inboxes (ab1+x@, 12345+x@) get a keyword that finds their
same-inbox siblings.

On a labeled fixture of 41 pairs (test/fixtures/pairs.js), 1.0.0 makes
13 errors (9 false positives, 4 false negatives); this makes 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: order the README from first look to fine print

Pitch, install, one quick start, what counts as a sibling, lookups, API
reference as tables, then edge cases. Same facts, 260 to 213 lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test: lock the 3-character mailbox and the second Gmail lookup

Raising the numbered-mailbox minimum from 3 to 4 stayed green, and the
README said any sibling skips the other Gmail domain. A numbered hit
below minSiblings still has to search it.

Co-authored-by: Cursor <cursoragent@cursor.com>

* test: lock trailing counter when both ends are numbered

Preferring the l... (continued)

120 of 120 branches covered (100.0%)

Branch coverage included in aggregate %.

112 of 112 new or added lines in 1 file covered. (100.0%)

248 of 248 relevant lines covered (100.0%)

45231.04 hits per line