Skip to content
Project guidePublic repo reviewed

is-malicious: Decomposing maliciousness into reviewable signals

You should be able to explain is-malicious in four sentences: what enters the system, what Jev judges, what code executes, and what independently proves the job finished.

Use caseFind uncertain results, risk signals, and items needing review

Source · luantak/is-maliciousSome code8 min

decomposing maliciousness into reviewable signals instead of one fuzzy Noul

Source · luantak/is-malicious · Open-source project

Public sources present this project for decomposing maliciousness into reviewable signals instead of one fuzzy Noul. This site has not reproduced the full project.

GitHub Open Graph preview for the luantak/is-malicious repository; a repository preview, not a screenshot of running software. Notes are based on its public source.

GitHub Open Graph preview for the luantak/is-malicious repository; a repository preview, not a screenshot of running software. Notes are based on its public source.

Find uncertain results, risk signals, and items needing review

Based on the public repository; this site has not reproduced the full project. Read the source before deciding whether to try it.