Security

Purpose

Services (previously known as DevTools) serve as a "purgatory" for services that are important to know about when working in Web3, but that doesn't have it's own unique category. Please note, that only web3-specific services are accepted for this category.

Storage path

references/offers/security.csv - canonical source for all new offers (including offers only exist one network). listings/specific-networks/<network_name>/security.csv - use !offer:<slug> references and only specify network-specific overrides when needed. listings/all-networks/security.csv - use for entries that should propagate to all network JSON outputs.

When to add

• Always create or update the canonical offer in references/offers/security.csv first.
• In listings, add !offer:<slug> and fill only fields that must override offer defaults.
• Tool is directly useful for building on this chain.
• Docs/install links are public and maintained.

Example

slug,provider,offer,actionButtons,tag,description,planType,planName,price,trial,starred,toolType,deliveryType,executionEnvironment,coverage,compliance
echidna,Echidna,"[""[Website](https://github.com/crytic/echidna)""]","[""Smart contract security"",""Fuzzing""]","Open-source property-based fuzzer for Ethereum smart contracts",Free,,$0,FALSE,FALSE,smart contract security,CLI,,"[""smart contracts""]",

Columns

slug

Refer to Common Columns.

provider

Refer to Common Columns. Examples: Hardhat, Foundry.

actionButtons

Refer to Common Columns.

tag

Refer to Common Columns.

description

What the tool does. Blank: No Format: text Examples: Open-source property-based fuzzer for Ethereum smart contracts

price

Refer to Common Columns.

planName

Refer to Common Columns.

planType

Refer to Common Columns.

trial

Refer to Common Columns.

starred

Refer to Common Columns.

toolType

Security tool primary category. Blank: Yes Format: text Examples: Audits, Compliance checker. Tips:

• Create additional category beyond one mentioned in examples only if you are absolutely sure that that none of the existing categories fits in, and explain its necessity in your PR.

deliveryType

How the tool is delivered/used. Blank: Yes Format: text Examples: CLI, Web app, API, SDK Tips:

• Create additional deliveryType beyond one mentioned in examples only if you are absolutely sure that that none of the existing categories fits in, and explain its necessity in your PR.

executionEnvironment

If it is limited by specific environment - point it here. Blank: Yes Format: text Examples: EVM, Substrate, Rust, etc.

coverage

What it covers / protects. Blank: Yes Format: JSON list Examples: "[""smart contracts""]", "[""token standards"",""DeFi protocols""]"

compliance

Compliance/security standards or frameworks supported. Blank: Yes Format: JSON list Examples: ["SOC 2"], ["ISO 27001"]