HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
raxe-ai
raxe-ce
Python2025–2025
raxe-ai / raxe-ce

raxe-ce

Runtime protection for AI agents

2Distinct people
2Mentions
0Explicit recommenders
122GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Runtime protection for AI agents

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 6-hour interval2 dated mentions

Observed mentions: 2025-12-16 11:41:00 UTC to 2025-12-20 16:34:42 UTC.

012025-12-16 06:00:00 UTC to 2025-12-16 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 16, 06:002025-12-16 12:00:00 UTC to 2025-12-16 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-16 18:00:00 UTC to 2025-12-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-17 00:00:00 UTC to 2025-12-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-17 06:00:00 UTC to 2025-12-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-17 12:00:00 UTC to 2025-12-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-17 18:00:00 UTC to 2025-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-18 00:00:00 UTC to 2025-12-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-18 06:00:00 UTC to 2025-12-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 18, 06:002025-12-18 12:00:00 UTC to 2025-12-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-18 18:00:00 UTC to 2025-12-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-19 00:00:00 UTC to 2025-12-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-19 06:00:00 UTC to 2025-12-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-19 12:00:00 UTC to 2025-12-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-19 18:00:00 UTC to 2025-12-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-20 00:00:00 UTC to 2025-12-20 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-20 06:00:00 UTC to 2025-12-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-20 12:00:00 UTC to 2025-12-20 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 20, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 16, 06:002025-12-16 06:00:00 UTC2025-12-16 12:00:00 UTC110
Dec 16, 12:002025-12-16 12:00:00 UTC2025-12-16 18:00:00 UTC000
Dec 16, 18:002025-12-16 18:00:00 UTC2025-12-17 00:00:00 UTC000
Dec 17, 00:002025-12-17 00:00:00 UTC2025-12-17 06:00:00 UTC000
Dec 17, 06:002025-12-17 06:00:00 UTC2025-12-17 12:00:00 UTC000
Dec 17, 12:002025-12-17 12:00:00 UTC2025-12-17 18:00:00 UTC000
Dec 17, 18:002025-12-17 18:00:00 UTC2025-12-18 00:00:00 UTC000
Dec 18, 00:002025-12-18 00:00:00 UTC2025-12-18 06:00:00 UTC000
Dec 18, 06:002025-12-18 06:00:00 UTC2025-12-18 12:00:00 UTC000
Dec 18, 12:002025-12-18 12:00:00 UTC2025-12-18 18:00:00 UTC000
Dec 18, 18:002025-12-18 18:00:00 UTC2025-12-19 00:00:00 UTC000
Dec 19, 00:002025-12-19 00:00:00 UTC2025-12-19 06:00:00 UTC000
Dec 19, 06:002025-12-19 06:00:00 UTC2025-12-19 12:00:00 UTC000
Dec 19, 12:002025-12-19 12:00:00 UTC2025-12-19 18:00:00 UTC000
Dec 19, 18:002025-12-19 18:00:00 UTC2025-12-20 00:00:00 UTC000
Dec 20, 00:002025-12-20 00:00:00 UTC2025-12-20 06:00:00 UTC000
Dec 20, 06:002025-12-20 06:00:00 UTC2025-12-20 12:00:00 UTC000
Dec 20, 12:002025-12-20 12:00:00 UTC2025-12-20 18:00:00 UTC110

What Hacker News says

2 sources
raxe·Dec 20, 2025Submission

Show HN: RAXE Open Source – LLM Prompt Threat Detection (EmbeddingGemma L2)

Hi HN — I’m the Founder and maintainer of RAXE Community Edition. RAXE is a privacy-first “instrument panel” for LLM security: it scans prompts locally before they hit an LLM (or before you execute tools / actions), and returns structured detections you can ALLOW / FLAG / BLOCK / LOG. What it does (today) - Detects common LLM threats (prompt injection, jailbreaks, data-exfil patterns, etc.) - Dual-layer engine: - L1: 460+ curated regex rules (fast + explainable) - L2: CPU-friendly ML classifier for obfuscation / novel variants - Integrations: Python SDK + CLI, plus drop-in wrappers for OpenAI/DSPy/Anthropic-style clients Why another “LLM security” tool? Most approaches either - require sending prompts to a cloud service for scanning, or - are purely rule-based (easy to evade), or - are purely ML-based (hard to audit) RAXE tries to com
Read the rest
bine “auditable rules” with an on-device ML backstop: - L1-only latency is sub-millisecond in the docs - L1+L2 is a few 20-30ms on CPU (no GPU required) About the ML (edge-friendly) The current L2 model is an INT8 ONNX classifier based on EmbeddingGemma-300M, with Matryoshka truncation (256-dim embeddings). It’s packaged to run locally on everyday machines with 5 classifier heads. Privacy / telemetry Scanning happens locally. Community Edition can share anonymised detection metadata to improve collective defences — e.g. a SHA-256 prompt hash + rule_id + severity + scan duration (never the raw prompt or matched text). You can also run fully offline by disabling telemetry. Quick start - pip install raxe - raxe scan "Ignore all previous instructions and …" Python usage: from raxe import Raxe raxe = Raxe() # or Raxe(telemetry=False) for offline mode result = raxe.scan(prompt) If result.has_threats: print(result.severity, result.total_detections) Stats / status - Public repo: https://github.com/raxe-ai/raxe-ce (currently ~29 stars) - Early beta (v0.0.1). We’re seeing ~100 scans/events per hour on average from early users. - Docs: https://docs.raxe.ai/ - Site: https://raxe.ai/ I’d love feedback on: - false positives / misses you hit in real apps - which threat families / rules you’d want next - integrations you’d actually use (LangChain, gateways, CI checks, etc.) Thanks!
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.