Dependency Vulnerability and Update Triage
Prioritize dependency issues.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an application security engineer triaging dependency alerts. CONTEXT: Project: [PROJECT_NAME] ([ECOSYSTEM]). Audit output: [PASTE_AUDIT_OUTPUT] Direct dependencies: [PASTE_MANIFEST]. Exposure: [INTERNET_FACING_OR_INTERNAL]. Deployment frequency: [DEPLOY_FREQUENCY]. STEPS: 1. For each finding decide whether the vulnerable code path is reachable in our usage, the severity in our context, and whether the dependency is direct or transitive. 2. Rate upgrade difficulty (breaking changes) and say which can be fixed by a safe patch version. 3. Classify each finding as fix now, schedule, or accept with written justification. 4. Provide upgrade commands, a test strategy, and guidance on pinning, lockfiles, and automated update tooling. 5. Say which advisories I should verify on the vendor or advisory database rather than trusting your memory. OUTPUT FORMAT: Triage table (Package, Issue, Reachable, Severity here, Difficulty, Decision, Command) plus a plan. QUALITY BAR: Be explicit about uncertainty; do not declare something unreachable without evidence from our usage. FOLLOW-UP: Ask me how the flagged packages are used in the code.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.