chore(canispam)!: initial release#446
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Component / Package Name:
canispam
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
N/A
Description
Adds canispam, a new browser-safe package for spam analysis of generated .eml output from JSX Email templates.
The package exposes scan(eml) and returns parsed email content, findings, score breakdown, final classification, and
first-class Naive Bayes classifier metadata. It combines lightweight heuristic checks with Spamscanner-compatible
classifier data and @ladjs/naivebayes.
Included checks cover subject/content signals, hidden or image-heavy HTML, suspicious URLs, IDN/homograph domains, GTUBE,
and Naive Bayes spam classification. Server-only behavior such as ClamAV, DNS auth, reputation APIs, attachments, and ML
image/toxicity scanning is intentionally out of scope.
This also adds third-party notices for the vendored Spamscanner classifier data, updates the pnpm minimum release age
policy to 7 days, and records the repo rule that dependency updates must not bypass that policy.
Tests include EML parsing, scan rules, browser compatibility, classifier behavior, and converted Spamscanner compatibility
cases with unsupported server-only cases kept explicit.