Skip to content
SkillModel-led2,321 tokens in use

entry-point-analyzer

Finds every state-changing entry point in a smart contract codebase and sorts them by access level for audit planning.

8,319 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/entry-point-analyzer/skills/entry-point-analyzer
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing entry-point-analyzer costs

112tokens idle
2,321tokens in use
10,105tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure23/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources13/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 71

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

Entry Point Analyzer maps the attack surface of a smart contract project. It detects the language (Solidity, Vyper, Solana, Move for Sui and Aptos, TON, CosmWasm), lists externally callable functions that change state, and classifies each one as public, role-restricted, restricted pending review, or contract-only.

Read-only functions are left out on purpose. The result is a structured markdown report with file and line references, ready to guide an audit.

What You Get

  • A markdown report with counts per access category
  • Tables of public, role-restricted, review-required and contract-only entry points with file and line
  • Notes on modifiers and inherited access control for each function
  • A list of files analyzed and any that could not be parsed

Common Use Cases

  • Starting a smart contract audit by mapping what anyone can call
  • Listing privileged operations such as upgrades, pausing and fee setters
  • Checking that callbacks really restrict their caller
  • Scoping a review to one directory of a large protocol

What Makes It Unique

It covers six contract ecosystems in one skill, with seven reference files, and it classifies access with care: a callback name or an msg.sender != tx.origin check does not count as access control, and unclear cases are flagged for review so the auditor makes the call. It also lists rationalizations to reject, such as “the modifier name is clear”.

Under The Hood

The skill is prose plus per-language reference files and no bundled scripts. The agent reads and searches the contract source and, for Solidity, checks whether Slither is installed with which and runs its entry-points printer in the project folder. If Slither is missing or fails, it falls back to manual reading. It does not fetch web pages and writes only the report it produces.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers