THE LAST RESORT
When a disclosure goes nowhere, it doesn't have to disappear.
A safe, private place for researchers to log stalled, ignored or poorly triaged vulnerability disclosures, using high-level facts only, so the pattern becomes visible: who answers, who fixes, and who lets cases sit.
1Report to the vendor firstUse their VDP, bounty or security contact.
→2It stallsNo reply, closed without a fix, triage limbo.
→3Log the facts hereDates, status, class. No exploit detail.
→4Private reviewA person reads every case. Nothing auto-publishes.
→5Aggregate mapCounts and trends; names only with 3+ independent reports.
Approved cases0
Awaiting review0
Organizations named0
Submit a stalled case privately See the accountability map I represent an organization
Who it's for
- Researchers who reported a vulnerability in good faith and got silence, a closed ticket with no fix, a disputed duplicate or months in triage.
- Cases where the facts (dates, status, class of issue) are useful for oversight and trend-spotting, even without any technical detail.
- Anyone, named or anonymous. Your handle and contact stay private.
What it isn't
- Not a place to publish a vulnerability. Never send exploit code, proof of concept, payloads, reproduction steps, credentials or personal data. The form refuses them.
- Not a bug bounty, CERT, regulator or legal service. ORBIT can't mediate, pay, or give you permission to test anything.
- Not a way to pressure or shame anyone. The map uses neutral counts, and every organization gets a right of reply.
The rules, short version
- Report to the vendor first, and follow their rules and the law.
- High-level facts only. Every case is held privately and read by Cloudy_Day before anything is counted.
- Approved cases appear only as aggregates by sector, program type and vulnerability class.
- An organization is named only after Cloudy_Day approves it and at least 3 independent researchers have approved reports about it.
- Organizations can reply, correct or ask for review at any time.