The Knowledge Base is the library behind the platform’s findings. Every detector, exploit, attack pattern, and remediation guide lives here, for EVM, SVM, and ZK alike, in one place you can browse and filter — so when a finding names a vulnerability class, the full write-up on what it is and how to fix it is a click away.
Why it exists
A finding is only as useful as the understanding behind it. When the engine flags a reentrancy or an under-constrained signal, you want the reference material: what the class is, how it’s exploited, and the concrete remediation. The Knowledge Base collects that material into a single browsable surface instead of scattering it, and covers all three runtimes so a team working across chains reads from one library.
Who uses it
- Auditor — reads the detector and remediation entry behind a finding to write it up accurately.
- Developer — looks up a vulnerability class and its fix while hardening a contract.
- Researcher — surveys the coverage across a runtime to see what is documented.
How to open it
- Sidebar → Knowledge Base.
- Direct URL —
/knowledge-base.
Browsing
Entries are grouped by kind — detectors, exploits, attack patterns, and remediation guides — and default to a severity-first order so the highest-impact classes lead rather than one runtime dominating the first screen. Filter by severity (from critical down) and by runtime to narrow to what you care about, and open any entry for the full write-up.
Limits
- The Knowledge Base is reference material about vulnerability classes, not results for a specific contract — run an analysis to get findings for your target, then follow them back here for the detail.
- It shows published entries; classes still on the roadmap may not yet appear.
Related pages
- Library — the broader content surface this reference sits within.
- EVM Contract Overview — where a finding links out to its Knowledge Base entry.