Red Flag Radar scans SEC EDGAR filings and surfaces accounting, audit and governance red flags: restatements, going-concern, auditor changes, late filings. Each one is scored, linked to the source filing, and free to browse. Plus a point-in-time forensic features API for builders.
No reviews yetBe the first to leave a review for Red Flag Radar
Maker
📌
Hi Product Hunt
I built Red Flag Radar because SEC filings are public, but the red flags inside them are not obvious. A restatement, a going-concern doubt, an auditor resignation, a late filing: these are some of the strongest signals in a company's disclosures, and they sit buried in 8-Ks and 10-Ks that almost nobody reads.
Red Flag Radar scans EDGAR continuously and turns those filings into structured, scored red flags. Every one is deterministic (no black box), computed point-in-time, and linked to the exact filing and the language that triggered it.
Free:
- Browse red flags by company, by type, or the daily feed
- RSS and a public JSON endpoint
- A weekly and monthly report
For builders: a point-in-time, evidence-backed forensic features API (issuer risk snapshots, auditor-change intelligence, restatement severity, and more).
It is a solo project, and the dataset grows every day. These are factual reports of public filings, not allegations of wrongdoing and not investment advice.
I would love feedback on: which red flags you would want added, how the false-positive handling feels, and what would make the API genuinely useful in a backtest or workflow. Ask me anything.
Report
💎 Pixel perfection
How often do you refresh the filings and update the scores, and does the API let me pull historical red flag data for a specific ticker going back a few years?
Refresh: EDGAR is polled continuously through the day, so a new 8-K or 10-K is picked up and scored within [X] of hitting the SEC. Scores are point-in-time: once a flag is computed as-of a filing date it never silently changes — if a later rule version would score it differently, the original stays intact and the new one is versioned alongside it. No look-ahead.
Historical by ticker: yes, that's the core of it. The API returns the full point-in-time history for an issuer, so you get every flag as it would have looked on the date it was filed, which is what you need for a clean backtest with no survivorship bias (companies that later delisted or went bankrupt stay in the data). Depth depends on tier; happy to send you a sample for a specific ticker if you want to see the shape before touching the API.
Report
Linking every flag straight back to the actual SEC filing instead of a hand-wavey summary is the right call, makes the whole thing feel built by people who actually do diligence.
Report
Maker
@yusufbakkuxn Appreciate that, Yusuf, it's exactly the bet. Anyone can post a summary; linking each flag to the filing and the specific triggering language is what makes it checkable rather than trust-me. That verifiability is the whole product, so it's good to hear it lands.
How often do you refresh the filings and update the scores, and does the API let me pull historical red flag data for a specific ticker going back a few years?
@emelzgbk Thanks Emel, two good questions.
Refresh: EDGAR is polled continuously through the day, so a new 8-K or 10-K is picked up and scored within [X] of hitting the SEC. Scores are point-in-time: once a flag is computed as-of a filing date it never silently changes — if a later rule version would score it differently, the original stays intact and the new one is versioned alongside it. No look-ahead.
Historical by ticker: yes, that's the core of it. The API returns the full point-in-time history for an issuer, so you get every flag as it would have looked on the date it was filed, which is what you need for a clean backtest with no survivorship bias (companies that later delisted or went bankrupt stay in the data). Depth depends on tier; happy to send you a sample for a specific ticker if you want to see the shape before touching the API.
Linking every flag straight back to the actual SEC filing instead of a hand-wavey summary is the right call, makes the whole thing feel built by people who actually do diligence.
@yusufbakkuxn Appreciate that, Yusuf, it's exactly the bet. Anyone can post a summary; linking each flag to the filing and the specific triggering language is what makes it checkable rather than trust-me. That verifiability is the whole product, so it's good to hear it lands.