Code4rena company primary sources — 2026-08-09

Entity-split status in this pass

• Code4rena now clears the bar for companies/ rather than staying as a standalone projects/ note.
• The useful question is not just what competitive audit format exists? but which named operator controls contest intake, judging, duplicate handling, public report publication, and the newer curated Zenith lane?
• The clearest current sources of truth in this pass were the homepage, the reports archive surface, the historical contest README, and the linked Zenith site.

Primary-source snapshots

1) Official Code4rena homepage

• URL: https://code4rena.com/
• Fetched: 2026-08-09 via web_fetch
• Key excerpt:
  • The homepage says Code4rena has completed 510 audits, surfaced 1,607 unique high severity vulnerabilities, found 26,898 unique findings, and has 16,600+ registered wardens.
  • The live page also shows active, completed, and report-in-progress audits under one operator-run shell rather than presenting Code4rena as a static archive.
  • That matters because the company boundary is not only a brand; it is the place where contest intake, audit visibility, and researcher-market access are packaged.

2) Reports archive surface

• URL: https://code4rena.com/reports
• Fetched: 2026-08-09 via web_fetch
• Key excerpt:
  • The reports surface is sparse in the fetch output, but it still exposes a dedicated Security Audit Reports page with sort and date-range controls.
  • Even that limited fetch is useful because it confirms public report publication is a first-class product surface rather than an accidental blog trail.

3) Historical contest-repo README

• URL: https://raw.githubusercontent.com/code-423n4/code-contests/main/README.md
• Fetched: 2026-08-09 via web_fetch
• Key excerpt:
  • The README says This repo is soon to be deprecated.
  • It then says all up-to-date information is on the C4 website and that contests are announced via the website, Discord, and Twitter.
  • That is useful because it makes the move from repo-native contest coordination to the company-run platform explicit.

4) Zenith audit offering

• URL: https://code4rena.com/zenith
• Fetched: 2026-08-09 via web_fetch (redirected to https://www.zenith.security/)
• Key excerpt:
  • Zenith markets itself with Good audits now. Not next month. and says customers choose Zenith when performance matters.
  • The site highlights 30+ prize-winning competitive hackers on our roster and <24h average lead time to start an engagement.
  • That matters because it shows Code4rena now packaging a curated, faster-start audit lane alongside the broader competitive marketplace rather than leaving the company surface confined to open contests.

Working conclusion

Code4rena is better modeled as a company-run competitive-audit, judging, and report-publication boundary than as a standalone project. The deciding evidence in this pass was the combination of a scaled operator-run marketplace, a dedicated reports surface, an explicit migration from public contest repos to the company website, and the linked Zenith offering that turns contest-market reputation into a curated audit product.