You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Security reports often fail for preventable reasons:
22
22
- a Critical RCE claim lacks a safe repro, tested version, or root-cause chain
23
23
- similar issues are already public in GitHub issues or PRs
24
24
25
-
Verifymate acts like a checklist-driven review partner: it compares the report to a checkout, highlights confirmed evidence, flags weak spots, and lists the questions a maintainer is likely to ask.
25
+
Verifymate acts like a checklist-driven review partner: it compares the report to a checkout, highlights confirmed evidence with file/line snippets, flags weak spots, and lists the questions a maintainer is likely to ask.
26
26
27
27
## What it checks
28
28
@@ -31,6 +31,7 @@ Verifymate acts like a checklist-driven review partner: it compares the report t
31
31
- The report includes an attacker model.
32
32
- The report includes a PoC/repro indicator.
33
33
- Dangerous capability terms exist in the repo.
34
+
- Line-level evidence locations show where referenced files, symbols, endpoints, and risky capabilities were found.
34
35
- Agent/tool context is detected so intended functionality is not mislabeled as RCE.
35
36
- Critical/High RCE reports include MADBugs-style proof context:
0 commit comments