Practical overview
When it fits
Use it during local development or security review when a Solana or Anchor codebase needs command-line static analysis, configurable findings and report output.
Who it is for
- Solana and Anchor developers
- Rust smart-contract security reviewers
- Engineering teams performing local code analysis
- Developers extending checks with custom rules
Documented uses
- Analyze Solana projects or selected Rust files
- Detect documented vulnerability and security patterns
- Review code-quality findings by severity
- Generate Markdown analysis reports
- Inspect available rules and individual rule information
Requirements & limits
The repository is public, identifies an AGPL-3.0 license and is documented for CLI or source builds. No pricing or account requirements are documented.
- It targets Solana and Anchor projects rather than general-purpose codebases.
- The documented workflow runs locally through a CLI or source build.
- Reports can be written to a file, while AST and verbose output support investigation.
- Findings can be filtered by severity or selected rules.
- The repository documents a DSL for writing custom rules.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Eloizer’s CLI and verify the executable
Set up the documented command-line tool and check that Eloizer responds to a version request.
Before you start
- A local copy of the Eloizer repository
- Rust and Cargo available for the documented Cargo installation command
Steps
Clone the repository and change into its directory.
Install the CLI with Cargo using the repository’s CLI path.
Run the documented version command to verify the installation.
Expected outcome
The Eloizer CLI is installed and responds to the version check.
Guide limitations
- Installation verification does not document an analysis result.
Analyze a Solana project and write a report
Run the documented CLI analysis against a Solana project path and save the findings as a Markdown report.
Before you start
- An installed Eloizer CLI
- A Solana project or Rust source path to analyze
Steps
Provide the project or source directory with the analyze command’s path option.
Add the output option with a Markdown filename.
Run the command and inspect the generated report.
Expected outcome
Eloizer analyzes the selected path and writes the report to the specified file.
Guide limitations
- The documentation does not establish the completeness or accuracy of findings.
- The supplied commands show example paths and do not document project-specific configuration.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 1 October 2026
- Original website title
- Inversive-Labs/eloizer · Official homepage title · retained in its source language