Practical overview
When it fits
Use it when you want to produce a Markdown artifact from static analysis of a Solidity contracts directory, with optional scope and repository-link settings.
Who it is for
- Solidity developers who want a command-line analysis step for contract code.
- Reviewers who need a scoped analysis report in Markdown.
Documented uses
- Analyze contracts in a specified directory.
- Limit the analysis to contracts listed in an optional scope file.
- Generate a Markdown report with optional GitHub links.
Requirements & limits
The repository is public and licensed under GPL-3.0. Installation requires Node.js and Yarn.
- The tool is run from the command line and takes a relative contracts-directory path.
- Scope files and GitHub URLs are optional inputs.
- Remappings are supported through a
remappings.txtfile placed in the contracts directory. - The output is a
report.mdfile.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install 4Naly3Er
Prepare the repository's documented command-line tool dependencies.
Before you start
- Node.js
- Yarn
Steps
Clone the 4Naly3Er repository.
Run
yarnin the cloned repository.
Expected outcome
The README identifies this as the installation step before using the tool.
Guide limitations
- These steps cover installation only; they do not verify execution or compatibility with a particular project.
Generate a Markdown report from contracts
Run the documented analysis command on a contracts directory and save its findings as Markdown.
Before you start
- 4Naly3Er installed with Node.js and Yarn.
- A relative path to a directory containing smart contracts.
Steps
Run
yarn analyzewith the relative path to the contracts directory.Optionally add a scope file argument to specify the contracts in scope.
Optionally add a GitHub URL argument to generate GitHub links in the report.
For remappings, place
remappings.txtin the contracts directory.
Expected outcome
The tool saves its output in a `report.md` file.
Guide limitations
- Scope file and GitHub URL arguments are optional.
- The documentation describes report generation and does not establish that a report is a complete security assessment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- Picodes/4naly3er · Official homepage title · retained in its source language

