---
title: "sublime-rules"
pageType: "tool-profile"
schemaVersion: "1.0"
snapshotId: "tv-20260911-8ab5e3f1311b"
generatedAt: "2026-09-11T07:01:56.000Z"
canonicalUrl: "https://toolvitals.com/tools/sublime-rules/"
jsonUrl: "https://toolvitals.com/api/agent/tools/sublime-rules"
indexable: true
---

# sublime-rules

Sublime rules for email attack detection, prevention, and threat hunting.

## Decision context

- Status: active
- ToolVitals score: 90/100
- Health score: 92/100
- Shipping score: 87/100
- Score mode: verdict
- Data confidence: 90/100
- Source coverage: 80/100
- Last evidence check: 2026-09-10

## Classification

- Use case: Email Security (email-security)
- Category: Security & Compliance (security)
- Tool mode: Source-visible project
- Openness: OSI-approved OSS
- License: MIT
- Tags: email, open-source, email-security, phishing, threat-hunting, attack-detection

## Public repository signals

- Repository: [sublime-security/sublime-rules](https://github.com/sublime-security/sublime-rules)
- Stars: 373 (adoption context only)
- Forks: 99
- Open issues: 70
- Last commit date: 2026-09-10
- Releases in 90 days: 0

## Source receipts

- [Official website](https://sublime.security/) — checked 2026-09-10
- [Source repository](https://github.com/sublime-security/sublime-rules) — checked 2026-09-10

## Discovery status

- Search indexable: yes
- Reason: sufficient tool evidence

## Interpretation limits

- ToolVitals scores summarize bounded public maintenance, shipping, openness, and evidence signals. They are not user-review ratings.
- GitHub stars and related popularity metrics are adoption context, not quality evidence.
- Missing values mean not collected or not confidently established; they do not mean zero.
- Public signals do not prove security, uptime, support quality, customer satisfaction, or production suitability.
- Verify material decisions against the linked first-party sources and your own requirements.