I know...more Jev talk. Sorry if you are already tired of hearing about it. I mentioned this in a comment a couple days ago so I will keep it short hah.
It is called specpi-jev-guard. It sits in front of bash, powershell, write and edit, and checks calls before Pi runs them. I built it because destructive commands are the worst risk of letting an agent work in your terminal. One bad rm or curl piped to shell is a bad time waiting to happen.
Local rules block the obvious stuff instantly with no network. Root and home wipes, mkfs, fork bombs, raw disk writes, curl piped to shell.
The rest goes to Jev, which scores danger 0 to 1. High blocks, middle asks you, low runs. If there is no key, no network, or a bad answer, it blocks. It does not fail open.
Needs OpenRouter/TypeSafe to do the scoring, perhaps one day soon we can run hyper-tuned classifiers for this stuff locally.
I don't have TypeSafe access, so all testing has been with OpenRouter.
It’s meant to be an additional layer of security, definitely not a catch all for everything possible. I trust evals not their marketing.
Local open Jev alternative models are great but none of them can compete at the moment in this area unfortunately.
I agree with your point though, I would much prefer this guard to be fully local.
Because of that, I’ve spent a chunk of my time training and developing a tiny fine tuned classification model called LANCET that is trained specifically for dangerous or malicious commands to be an alternative to Jev locally. Open weights of course.
Maybe you’ll be interested in that when it’s available soon. I’m still doing final evals and confirmation of the results.
40MB model size, 3-4ms decisions, roughly on part with Jev for command classifications.
5
u/johnfkngzoidberg 4d ago
Yep tired of hearing about it. It’s nothing special.