Skip to content

Commit c6155e2

Browse files
author
TOUGH LOVE SECURITY
committed
docs: add SECURITY.md with 90-day disclosure policy
1 parent 50692e6 commit c6155e2

1 file changed

Lines changed: 35 additions & 0 deletions

File tree

SECURITY.md

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
# Security Policy
2+
3+
## Reporting a Vulnerability
4+
5+
If you find a security issue in this scanner, please email **contact@toughlovesec.win** with:
6+
7+
- A description of the issue
8+
- Steps to reproduce (or a proof-of-concept)
9+
- Your assessment of severity
10+
11+
**Please do not** open a public issue, post to social media, or demonstrate the vulnerability against systems you do not own.
12+
13+
## What to expect
14+
15+
- Acknowledgement within 72 hours
16+
- Status update within 7 days
17+
- Coordinated disclosure timeline: **90 days** from initial report, or earlier if a patch ships and is adopted
18+
19+
We do not currently offer a paid bug bounty, but we credit reporters in release notes unless you request anonymity.
20+
21+
## In-scope
22+
23+
- `server.js` — the HTTP wrapper (auth bypass, RCE, path traversal, SSRF)
24+
- `scan.sh` and `scanners/*.sh` — the scan orchestrator (command injection via target URL, payload handling)
25+
- `Dockerfile` / `fly.toml` — deployment hardening concerns
26+
27+
## Out of scope
28+
29+
- Findings produced by the scanner on third-party sites
30+
- Denial-of-service against the scanner itself via malformed input (file issues for these)
31+
- Social engineering, physical attacks
32+
33+
## Responsible use
34+
35+
This tool sends active payloads. Only scan systems you own or have written authorization to test. Unauthorized scanning is illegal in most jurisdictions. We are not responsible for misuse.

0 commit comments

Comments
 (0)