New:Microsoft Teams Notifications Are Now Available in Socket.Learn more
Get Started

@mosadd/threat-engine

Package Overview
Dependencies
Maintainers
1
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@mosadd/threat-engine

Threat-event taxonomy (166 canonical events) + scoring + pure defensive-decision engine for mosadd. The kernel-level security primitive that becomes the radar moat in the Phase 2 hub.

Source
npmnpm
Version
3.0.0-alpha.26
Version published
Weekly downloads
73
135.48%
Maintainers
1
Weekly downloads
 
Created
Source

@mosadd/threat-engine

Threat-event taxonomy + scoring + pure defensive-decision engine. The kernel-level security primitive that becomes the radar moat in the Phase 2 commercial hub.

A module of mosADD — the comms layer for AI agents, and the humans who direct them.

What's in the box

  • evaluateEvent(event){ action, severity, reason } — a pure, backend-free decision function. It decides; the caller carries out the action (revoke sessions, lock account, suspend DID). No side-effects, no authority.
  • The full canonical taxonomyTHREAT_EVENTS (166 event types across SIGINT / COMINT / ELINT / MASINT / CYBER / BEHAVIORAL / PRIVACY / OSINT / MPOST), each with a default severity, auto-actions, and per-platform availability. Read THREAT_EVENT_COUNT / THREAT_EVENTS.length for the exact, live count — never a hardcoded marketing number.
  • Scoring & lookup helpersSEVERITY_SCORE, EVENT_BY_ID, getEventsByCategory, getEventsByPlatform, KILLSWITCH_EVENT_IDS, PLATFORM_EVENT_COUNTS.
import { evaluateEvent, THREAT_EVENTS, THREAT_EVENT_COUNT } from "@mosadd/threat-engine";

evaluateEvent({ eventType: "SIM_SWAP" }); // → { action: "lock_account", severity: "killswitch", ... }
THREAT_EVENT_COUNT;                        // → 166

Status

Alpha. The decision engine and the full taxonomy both ship in this package today. Runtime ML-scoring refinements continue across the v3.0.0-alpha line.

License

Apache-2.0.

FAQs

Package last updated on 27 Jun 2026

Related posts