mehen 0.2.0

Tool to compute and export code metrics

mehen

mehen is a Rust-powered CLI for detecting heuristic source code metrics at scale: complexity, maintainability, lines of code, and more.

It is designed for fast, deterministic analysis over large codebases, helping both human and AI engineers track how complexity evolves over time.

What is Mehen?

In Ophidiarium projects, names matter.

Mehen is a mythical ancient Egyptian serpent associated with guarding Ra. In the same spirit, mehen helps guard your codebase from slowly collapsing under complexity.

Why Teams Use Mehen

Most common usage patterns we see:

• CI jobs that compute metrics for changed files and publish trend reports
• Pre-PR / pre-CR hooks that provide immediate quality feedback
• Automation workflows that enrich pull request templates with metric deltas

Current Language Support

Today mehen supports:

• Python
• TypeScript
• TSX
• Rust
• Go
• Ruby

Planned next: PHP.

What Mehen Computes

mehen provides a broad metric set, including:

• Cyclomatic complexity
• Cognitive complexity
• Maintainability Index
• Halstead metrics
• ABC metrics
• NArgs / NOM / NExit
• LOC family (SLOC, PLOC, LLOC, CLOC, blanks)
• NPA / NPM / WMC

Distribution

mehen ships native binaries through both ecosystems:

• npm (mehen + platform packages)
• PyPI (mehen via maturin binary packaging)

Quick Start

Run without installation

From npm ecosystem:

bunx mehen --help

From Python/uv ecosystem:

uv tool run mehen --help
# or
uvx mehen --help

Run locally from source

cargo run -- --help

Typical examples

Analyze metrics for a directory:

mehen -m -p src

Export metrics as JSON/TOML/YAML/CBOR:

mehen -m -p src -O json -o ./metrics

GitHub Actions

Use the in-repository action to publish changed-file metric trends on pull requests:

permissions:
  contents: read
  pull-requests: write
  issues: write

steps:
  - uses: actions/checkout@v5
    with:
      fetch-depth: 0

  - uses: ophidiarium/mehen@v1
    with:
      paths: src

For polyglot monorepos, pass each root you want tracked. mehen will analyze only supported languages in changed files under those roots:

- uses: ophidiarium/mehen@v1
  with:
    paths: |
      crates/api/src
      apps/web/src
      tools
    thresholds: |
      cyclomatic=5
      cognitive=4
      loc.lloc=120

Thresholds are optional. When configured, the action fails if an adverse per-file metric delta exceeds the configured limit.

Reporting and Integrations

Current machine-readable outputs:

• JSON
• YAML
• TOML
• CBOR

Roadmap direction:

• Native git integration for changed-file detection
• Rich markdown reports for AI/human review flows
• More polished console reporting for local developer loops

Implementation Notes

Internally, mehen is built on:

• tree-sitter for parsing
• The excellent foundational work from Mozilla's rust-code-analysis

mehen continues in its own CLI-focused direction while preserving and evolving that foundation.

Development

Build and check:

cargo check
cargo build
cargo fmt --all
cargo clippy --all-targets --all-features --locked

Tests:

cargo test --all-targets --locked

Snapshot tests (insta):

cargo insta test --all-features --check --unreferenced reject --test-runner nextest --no-test-runner-fallback --disable-nextest-doctest

See mehen-book/src/developers/ for developer docs, including language and grammar updates.

Contributing

Contributions are welcome via issues and pull requests:

• https://github.com/ophidiarium/mehen/issues

License

mehen is released under the Mozilla Public License v2.0.