FYEO

• Name: FYEO
• URL: https://fyeo.io/
• Category: smart-contract security company / hybrid AI-plus-human audit workflow operator / public audit-corpus publisher
• Summary: FYEO belongs as an entity note, not a protocol note. The useful question is who packages the hybrid AI-plus-human review workflow, decides which risky diffs and third-party dependencies get emphasized, curates the public audit corpus, and turns multiyear report publication into a reusable trust and distribution surface. The practical control boundary sits in the named security company and its review, publication, and customer-engagement workflow rather than in a standalone deployed protocol.
• What it does:
  • Performs Web3 security reviews centered on AI-guided smart-contract audits with human expert validation
  • Publishes a first-party public audit repository with linked PDF reports and companion blog posts
  • Maintains a structured public audit matrix spanning multiple years, languages, client types, and protocol ecosystems
  • Packages security review, explanatory writeups, and report visibility into one named operator boundary rather than just shipping a neutral open-source analyzer
• Key claims:
  • FYEO’s site presents the company as “Hybrid AI + Human-Led Web3 Security Audits” and says its methodology uses “AI-guided smart contract audits with human expert validation”
  • The same site metadata says FYEO’s hybrid approach “pinpoints risky code diffs and third-party vulnerabilities,” which is more operationally specific than generic AI-audit branding
  • FYEO’s public audit repository exposes both a Code Audit Reports directory and a PublicAuditMatrix.md file, signaling that the company treats public reporting as a structured product surface rather than a loose marketing archive
  • The primary-source pass found the public audit matrix spanning 2021 through 2026 across dozens of clients and many protocol labels, with linked PDF reports and many first-party FYEO blog posts
  • The matrix breadth across Ethereum, Solana, XRPL/Xahau, Flare, Axelar, Cosmos-adjacent systems, wallets, and agent-related projects suggests FYEO is operating a reusable multichain review-and-publication workflow rather than servicing one narrow niche
  • The public GitHub organization surface is centered on the audit-report corpus itself, reinforcing that FYEO’s most important public artifact is the review and report library published under one company boundary
• Whitepaper: No canonical standalone FYEO whitepaper or litepaper surfaced in the source pass. The clearest current sources of truth remain the FYEO site metadata, the public audit-reports repository, and the public audit matrix; see ../whitepapers/fyeo-primary-sources-2026-05-03.md.
• Sources:
  • https://fyeo.io/
  • https://fyeo.io/blockchain-security-audit
  • https://github.com/fyeo-io
  • https://github.com/fyeo-io/public-audit-reports
  • https://raw.githubusercontent.com/fyeo-io/public-audit-reports/main/README.md
  • https://raw.githubusercontent.com/fyeo-io/public-audit-reports/main/PublicAuditMatrix.md

Internal linkages

• Project-layer alias: fyeo.
• Strongest adjacent company/operator comparison set: trail-of-bits, dedaub, zellic, and numen-cyber.
• Reusable lens: a security vendor deserves a company cut when the practical trust surface is the named operator’s review workflow, report-publication strategy, and customer-facing assurance shell rather than a durable protocol or neutral tooling primitive.

Protocol / company boundary

• There is no especially useful standalone FYEO protocol boundary doing the analytical work here.
• The important surface is the company’s hybrid review workflow, publication decisions, audit-corpus curation, and how customers or downstream readers treat FYEO’s reports as assurance signals.
• That is why FYEO belongs in companies/: the control question is who operates and publishes the review shell, not what immutable protocol supposedly replaces that judgment.

Control surface

• Practical leverage sits in review methodology, AI-versus-human triage balance, diff prioritization, third-party dependency emphasis, report scope, public-disclosure choices, and the visibility FYEO gives to some findings or client engagements over others.

• The public audit matrix matters because it turns one firm’s publication policy into a discoverability and reputation surface that can shape which ecosystems and issue classes receive recurring attention.

• Read FYEO as a company-run security-review and assurance-publication boundary, not as a neutral protocol primitive.

• Last reviewed: 2026-08-12 UTC