TriggerMap · demo

Under what conditions is a vulnerability reachable?

TriggerMap reads English security advisories for Python packages and suggests the deployment conditions they state: a setting, a feature in use, the attacker's access, a platform. Each item is a verbatim span of the advisory, with its role and logic, for a person to confirm or correct. These are three unedited outputs of the released model: one ordinary case, one hard case and one abstention.

Three real outputs

Ordinary case · mostly right

aiohttp directory traversal

GHSA-5h86-8mv2-jq9f

Finds the web-server use and the follow_symlinks setting, and does not turn "even when symlinks are not present" into a prerequisite. It also repeats overlapping spans, keeps a bare "set to True" fragment, and does not group the conditions.

Open the review page →
Hard scope case · partly right

Flask session cookie disclosure

GHSA-m2qf-hxjv-5gpq

The advisory lists five conditions that must all hold. The model finds two of them. It misses both required absences ("does not access or modify the session", "does not set a Cache-Control header") and the default-on SESSION_REFRESH_EACH_REQUEST, and it wrongly marks a background phrase as a requirement.

Open the review page →
Abstention · nothing found

Django MultiPartParser traversal

GHSA-xgxc-v2qg-chmh

The model finds no conditions, and the page says so plainly, without claiming the conditions do not apply. Both model drafts of this advisory mark the MultiPartParser requirement and the carve-out "built-in upload handlers were not affected"; the model finds neither.

Open the review page →