JevMade field notes / Written guide

Review an AI assistant's tools before running them

Jev Security Scan reads tool instructions, connection settings, and code before installation. It combines local checks with optional Jev review and reports evidence and blind spots rather than promising a security certificate.

Original by win4rGuardrails

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits and license

“Jev Security Scan” by win4r. Read the original source.

This expanded guide is an AI-narrated adaptation of the source’s essential explanation, examples and caveats, not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

License: MIT

MIT License

Copyright (c) 2026 win4r

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Our summary

Before installation, Jev Security Scan reads agent instructions, source code, and MCP settings—the configuration that connects AI software to outside tools. It reports suspicious credential access, hidden changes that survive restarts, downloaded code that runs immediately, and parts it could not inspect.

Offline checks use fixed rules and do not install dependencies, meaning extra software the target relies on. Optional Jev review sends snippets after redaction, which means replacing recognized secrets. It still may expose source text, while offline mode keeps the inspected material local.

A clean report is not a security certificate. Disguised code, unsupported files, missing context, and new attacks can escape both methods. Redaction can miss secrets, so sensitive projects should start offline and inspect exactly what optional review sends.

Key takeaways

Inspect untrusted tools before installing extra software or running them.
Use local-only checks when material must not leave the computer.
Keep evidence and unscanned areas visible beside findings.

More guides →See the experiments →