Add Code4rena, Sherlock and Immunefi audit platforms - #2452
Open
EazyHood wants to merge 4 commits into
Open
Conversation
The security category covers audit firms and analysis tools but has no entry for the competitive-audit and bug-bounty platforms that sit between them, even though they are how a large share of EVM protocols get reviewed today. Providers: - Code4rena time-boxed public audit contests - Sherlock competitive contests with structured judging - Immunefi continuous bug bounty programs One offer each, listed on ethereum, arbitrum and optimism. Every website, docs URL, GitHub org and X handle was resolved before submitting. All three logos are real PNGs -- github.com/immunefi-team.png serves a JPEG despite the extension, so the logo comes from the immunefi org avatar instead. Rows inserted in sorted position, so the diff is additions only. Rewards address: 0x06f44f4839fd5df4f4670036d028b29dec939363
Summary
Errors per inputErrors in ./references/providers/providers.csv
|
USS-Supervisor
requested changes
Aug 3, 2026
USS-Supervisor
left a comment
Member
There was a problem hiding this comment.
Verdict: REQUEST_CHANGES
Risk: MEDIUM
Summary: Required validation is passing and the current reviewer-owned link-check succeeded, but two of the new provider logo assets violate the provider-logo background rule.
Findings:
- MEDIUM
references/providers/images/code4rena.pngandreferences/providers/images/immunefi.png: both submitted PNGs are RGB images without an alpha channel and render on solid square backgrounds. The provider logo README requires transparent-background logos and rejects solid-background images except rare intentional brand-container cases. Please replace these with transparent-background PNGs, or document why the square background is intentionally part of the official brand mark.sherlock.pngalready has transparent corners and does not need the same fix.
Confidence: HIGH
CI/link-check:
- Required CI:
Generate JSON and validate (isolated)= SUCCESS - Current-cycle
link-check: SUCCESS (started 2026-08-03T05:01:40Z, completed 2026-08-03T05:01:47Z)
Updated the entry for 'Sherlock' in the providers list to correct the duplicate entry issue.
The row had 13 fields instead of 14: the empty supportEmail placeholder was missing, so FALSE landed in supportEmail and starred was dropped entirely. That is what Validate JSON was rejecting (row 539 has 13 columns, expected 14).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the three main competitive-audit and bug-bounty platforms, which the
securitycategory was missing entirely.The category already covers audit firms (Certik, Halborn, Quantstamp, Trail of Bits…) and analysis tools (Slither, Medusa, Halmos, Aderyn…). Between those two sits a third model — crowdsourced review with judged findings — and it is how a large share of EVM protocols actually get reviewed today. None of the three were present.
securityis listed as an under-covered expansion lane in this week's digest.What is added
Providers
code4renasherlockimmunefiOffers — one each:
code4rena-audit,sherlock-audit,immunefi-bug-bounty.The distinction is captured in
toolTypeandcoverage: contests are pre-deployment and time-boxed, the bounty program is post-deployment and continuous.Listings:
ethereum,arbitrum,optimism.Validation
github.com/immunefi-team.pngserves a JPEG despite the.pngextension. The file in this PR comes from theimmunefiorg avatar instead, which is a genuine PNG. Anyone bulk-fetching provider logos from GitHub will hit that.!offer:<slug>in the new listings resolves.git diff --checkclean.Scope
Companion to #2451 (Certora, Dedaub), which covers the formal-verification side of the same lane. The two touch the same files but different rows and should merge independently.
Rewards address:
0x06f44f4839fd5df4f4670036d028b29dec939363