Cybersecurity toolkits · Rank #3
flounder
Grade A: derived only from the two verdicts below. How grades work
Autonomous white-hat security auditor for AI-driven code review, bug bounty research, exploit construction, and execution-grounded verification.
Why this verdict
How we check →- 134 commits by 2 contributors in the last 90 days (43 in the last 30). receipt ↗
- On current major: React. receipt ↗
- Not counted in verdict: TypeScript 5 → 7. receipt ↗
Snapshot: commit 505571a on main, checked 2026-10-19 07:09 UTC. Receipts link to files at this exact commit.
Dependency freshness
| Package | Declared | Latest | Status |
|---|---|---|---|
| TypeScript typescript | 5.9.0 | 7.0.2 | Behind, not counted |
| React react | 19.2.7 | 19.3.1 | Current |
Declared = lowest version the kit's dependency file (package.json, pyproject.toml or requirements.txt) allows. Latest = the npm "latest" tag or the newest PyPI release. TypeScript, the Stripe SDK, FastAPI and other 0.x packages are shown but not counted in the verdict.
What's in the stack
- Framework
- Vite
Detected from declared dependencies. A listed package means it's installed, not necessarily fully wired up.
What the README says you get
- AdminGoverned maintainer experiments
helps a Flounder maintainer agent mine verifier-grounded Evaluation failures
- DeployLocal control of code and credentials
Audits run on a daemon, optionally on another machine, so target code and provider credentials stay on the executor host
- OtherBlind discovery plus reproduction
Discovery runs network-sealed, so findings are derived from the target material
- OtherMultiple audit scenarios
blind capability audits, incident investigation from suspicious on-chain evidence, open-world bug-bounty audits
- OtherSolidity and ZK fit
Solidity/EVM targets work well because local forks and Foundry/Hardhat tests can prove real on-chain effects
Extracted from the kit's README by a local AI model (deepseek-flash) on Oct 12, 2026. Every item is checked against an exact README quote; 9 unverifiable items were discarded. A README claim is the maker's description, not something we tested.
Watch flounder
Get told if it goes dormant, gets archived, falls further behind on a core dependency, or changes its license or price.
History
Sep 29, 2026 → Oct 19, 2026. One square per check, colored by maintenance status. Hover for details.
Show as a table
| Date | Maintenance | Dependencies | Commits (90d) |
|---|---|---|---|
| Oct 19, 2026 | Active | Current deps | 134 |
| Oct 12, 2026 | Active | Current deps | 169 |
| Sep 29, 2026 | Active | Current deps | 265 |
Sources
Every claim on this page comes from these public records, checked . Open them to verify.
- Commit history ↗ default branch (main) at the checked commit: pulse, contributors, last commit
- Releases ↗ latest release
- package.json ↗ declared dependency versions and stack (at commit 505571a)
- README ↗ quoted features at the checked commit
- npm registry ↗ latest versions (each linked in the table above)