
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest
by usestrixFree
Description
fix-security-vulnerabilities-with-strix is a skill from the Strix project for turning validated pentest findings into minimal, correct fixes, and then proving the fixes work by scanning again. It covers two sources of findings. From the open-source CLI, the findings sit in the run folder, one markdown file per vulnerability with its description, severity, proof of concept and remediation guidance, plus a JSON file with the same records and suggested code changes where available. From the managed cloud, the skill pulls findings with the strix cloud CLI and marks a fixed finding as fixed once verified. It orders the work by severity, from critical to low, and it warns not to dismiss a finding as a false positive without rerunning its proof of concept yourself, since each Strix finding was validated with a working proof of concept. For each finding it makes the fix at the root cause rather than at the symptom, and then re-scans to confirm the vulnerability is gone. It is for developers who have a pentest report and want the fixes done carefully and checked. Review each change before merging, and keep the proof-of-concept scripts out of production code. The skill shows warnings from Gen Agent Trust Hub and Socket on skills.sh, and Snyk passes. It has about 13,200 installs. Install it with npx skills add https://github.com/usestrix/strix --skill fix-security-vulnerabilities-with-strix.…
Highlights
- Triage by severity, from critical to low
- Reads findings from the CLI run folder or the Strix cloud
- Fixes the root cause, then re-scans to verify
- Marks cloud findings as fixed once verified
Ratings & Reviews
No ratings yet
Be the first to rate fix-security-vulnerabilities-with-strix.
People also visit
fix-security-vulnerabilities-with-strix FAQ
Where are the findings?
For the CLI, in strix_runs/<run-name>/, as markdown files and a JSON file. For the cloud, through the strix cloud CLI.
In what order are fixes done?
Critical first, then high, medium and low.
Can I dismiss a finding as a false positive?
Not without rerunning its proof of concept yourself, because each finding was validated with a working proof of concept.
How is a fix confirmed?
By re-scanning, so the verified fix can be marked fixed in the cloud.
How do I install it?
Run npx skills add https://github.com/usestrix/strix --skill fix-security-vulnerabilities-with-strix.
What are the best fix-security-vulnerabilities-with-strix alternatives?
Popular alternatives to fix-security-vulnerabilities-with-strix include application-security-testing, security-audit and api-security-testing. See all fix-security-vulnerabilities-with-strix alternatives







