JevMade Sign in
← Back to experiments

Apps & data pipelines

Jev IDS

Trained intrusion-detection models want thousands of labeled flows. This hands Jev five examples per attack type and gets close enough to be worth arguing about.

Bookmark: Jev IDS Keep this in your collection.
Leave a noteWhat would you try with this? : Jev IDS

Only you can see your notes.

Source screenshot of Jev IDS
SOURCE SCREENSHOTFull screenshot ↗

What it does

Full accuracy, precision, recall, and F1 sit beside a Gemini baseline in the README, and the baseline wins on F1. What Jev buys is latency, cost, and recall on attack types that were never in the examples.

How you can use it

Gather a few network activity records labeled as normal or suspicious traffic. Write brief descriptions for each attack category you want to spot. A developer can package each new connection record alongside your notes and sample records, then send them to the TypeSafe service.

The service returns an estimated chance of an attack and names the matching category. Your developer can feed these numbers into your security dashboards to flag unusual connections for review, though they remain automated estimates rather than guaranteed proof.

Maker-reported (not independently measured by JevMade): 7.7× faster and 22× cheaper than Gemini 3.6 Flash at k=1; precision 0.953 vs 0.942; 18× fewer false alarms than Random Forest (maker-reported)

Primitives
noul, choice
Platform
Python
Added
Project created

Keep this for later

Sign in to bookmark experiments, guides and videos, and keep notes only you can see.

Continue to sign in

We’ll bring you back to this listing.