Small decisions. Interesting possibilities.Submit contentSubmit
is-malicious preview

is-malicious

Scans a codebase for covert, deceptive, or data-stealing behavior with Jev, then reports suspicious files and line ranges before the user runs it.

Added to Jevfast

How it uses Jev

The scanner selects eligible text files, groups or slices their contents into bounded chunks, and sends chunk state with per-check Noul questions plus overall risk and category questions. Uncertain or suspicious chunks receive a focused second pass with line-window and reason Choices. Code compiles findings with paths and line ranges.

What Jev decides

Illustrative Jev requestExample answers · not a recorded Jev response · Source ↗
Question 1 · check
YOUR APP
INSTRUCTION

Does this chunk satisfy the configured semantic security check?

STATE

A bounded source-code text chunk and the scan check instructions selected for that chunk.

JEV · NOUL
YesNo

App workflow

  1. Select source files

    The CLI respects ignore and file filters, then partitions eligible content into chunks that fit the configured character budget.

  2. Run the first review pass

    Jev evaluates each chunk against registered checks and returns risk/category judgments.

  3. Focus follow-up checks

    Suspicious or uncertain chunks, and high-risk results, are revisited with targeted line windows and reason choices.

  4. Present findings and gaps

    The report shows suspicious file/line references, scores and coverage omissions; scan errors are distinguished from severity outcomes.

Why it is interesting

It combines broad first-pass screening with narrower follow-up and reports files it could not scan, making coverage limits visible. Results direct attention for human review and are not proof that a clean project is safe.