‹ Back to apps
SPHIOR CODE
sphior-code plugin for Cursor
What’s inside
4 skills- Skillfix-security-findingsFind and fix security problems in the current codebase with SPHIOR CODE — hard-coded secrets, insecure patterns mapped to CWE, and taint flows (untrusted input reaching a shell, SQL, eval, HTML, file-path or URL sink). Use when the user says things like "scan this project", "check this for vulnerabilities", "fix the security issues", "is there a SQL injection here", "any hard-coded keys?", or asks for a security review of a file or directory.
- Skillpre-release-security-checkRun a SPHIOR CODE security gate before a release, merge or deploy and give a clear ready / not-ready verdict — no exposed secrets and no open critical or high findings. Use when the user says "is this ready to ship", "check before release", "pre-merge security check", "can I deploy this", "final security pass", or is about to tag a version or open a release pull request.
- Skillsetup-security-ciAdd SPHIOR CODE security scanning to a project's CI — fail the build on serious findings and publish SARIF to GitHub code scanning. Use when the user asks to "add security scanning to CI", "scan every pull request", "block merges with secrets or vulnerabilities", "set up SAST in GitHub Actions / GitLab CI", or wants findings in the GitHub Security tab.
- Skilltriage-security-findingsReview SPHIOR CODE findings one by one and decide which are real, which are test fixtures or examples, and which are false positives — fixing the real ones and recording each accepted one with a written reason in .sphiorignore or an inline comment. Use when the user says "there are too many findings", "these are false positives", "this is test data", "clean up the scan results", "suppress this", or before turning on a CI gate on an existing codebase.