Made by@slashcloneSecurity audit for your web app before launch
@slashclone/security-review-checklist
Get a written security audit of your web app before launch or after a big feature. Covers the API, sign-in and OAuth, MCP connectors or CLIs, and file uploads, and writes a threat model plus numbered findings with severity, fix, and how each fix was verified. Reads the code and runs signed-out checks only; never changes your code.
SkillDevOpsv0.1.1 (latest)
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# Findings
- 3Review date: YYYY-MM-DD. Scope: see [architecture.md](architecture.md). Threats: see [threat-model.md](threat-model.md).
- 5Severity: **Critical** (exploitable now, broad harm), **High** (exploitable, real harm), **Medium** (needs conditions or limited harm), **Low** (defense in depth), **Info**.
- 7**Result:** N Critical, N High, N Medium, N Low. Open: N. Top risks: one line each.
- 9## Findings
- 11| ID | Severity | Area | Where | Impact | Fix | Verified how | Status |
- 12| ---- | -------- | ---- | ----- | ------ | --- | ------------ | ------ |
- 13| R-01 | | | | | | | Open |
- 15Status is one of: Open, Fixed, Accepted (with the reason and who accepted it).
- 17## Checked and fine
- 19- **Area:** what was checked, and the one line of evidence.
- 21## Open questions
- 23- Anything you could not check, and why (no test account, no access to a host, out of scope).