maleme

maleme is a local-first Rust toolkit for collecting user-authored prompt history from coding agents, extracting profanity usage signals, and producing a compact visual analytics report.

The CLI is already published to npm, so you can run it directly without a global install:

npx maleme
bunx maleme
vpx maleme

Map

• Quick Start
• Highlights
• Overview
• Architecture
• Supported Data Sources
• Profanity Lexicon
• Report Generation
• Development
• Install
• npm Release Flow
• Repository Metadata
• Star History
• Scope
• License

The project is designed around three practical requirements:

1. Unified ingestion of locally stored conversation history from multiple coding agents.
2. Deterministic detection and aggregation of profanity usage across multilingual user input.
3. Repeatable generation of a browser-friendly HTML report suitable for local review.

Quick Start

Run maleme directly from the published npm package:

npx maleme
bunx maleme
vpx maleme

Or install it globally:

npm install -g maleme

Highlights

• Local-only data processing with no mandatory hosted service dependency
• Unified adapters for Codex, Claude Code, and OpenCode
• Embedded multilingual profanity lexicon with file-based maintenance
• Single-file HTML report generation for lightweight sharing and inspection
• Token-normalized profanity metrics for cross-session comparison

Overview

maleme reads local chat history from supported coding agents, normalizes user-authored text input, computes profanity frequency metrics, and renders a standalone HTML report.

The current implementation supports:

• Codex
• Claude Code
• OpenCode

The generated report includes:

• Daily profanity frequency over time
• A normalized profanity intensity metric (SBAI)
• A word cloud of the most frequently used terms

Architecture

The repository is organized into a small set of focused modules:

• src/agent_adapter/ Adapter implementations for each supported coding agent. Each adapter is responsible for:

  • local availability checks
  • user-message extraction
  • token usage extraction

• src/fuck_detector.rs Profanity lexicon loading and text matching logic.

• src/report.rs Report data aggregation, HTML rendering, and local browser launch.

• data/profanity_lexicon.txt Editable profanity lexicon embedded into the compiled binary at build time.

Supported Data Sources

maleme operates against local files and databases already present on the host system. It does not require a remote service for analysis.

Current canonical sources:

• Codex:

  • ~/.codex/sessions/
  • ~/.codex/archived_sessions/
  • ~/.codex/state_5.sqlite

• Claude Code:

  • ~/.claude/transcripts/
  • ~/.claude/projects/
  • ~/.claude/stats-cache.json

• OpenCode:

  • ~/.local/share/opencode/opencode.db

Profanity Lexicon

The profanity lexicon is stored in:

• data/profanity_lexicon.txt

Format:

term one
term two
term three

Rules:

• one entry per line
• line number is treated as the entry code
• modifying the text file and rebuilding the project updates the embedded lexicon

Report Generation

Running the binary will:

1. scan supported local agent history
2. collect user-authored messages
3. calculate profanity metrics
4. generate a standalone HTML report in ~/Downloads
5. open the report in the local default browser

Development

Build:

cargo build

Run:

cargo run

Test:

cargo test

Install

Install the published CLI from npm:

npm install -g maleme

The npm distribution follows the same general pattern used by Codex CLI:

• maleme is the lightweight wrapper package
• maleme-<platform>-<arch> packages carry the native binaries
• the wrapper selects the right binary at runtime

Current npm targets wired in this repository:

• darwin-arm64
• darwin-x64
• linux-arm64
• linux-x64
• win32-x64

npm Release Flow

The repository includes a GitHub Actions workflow at .github/workflows/publish-npm.yml.

For the repeatable release checklist, see:

• docs/release-sop.md
• docs/npmjs-publish-sop.md

Release steps:

1. bump version in Cargo.toml
2. run node scripts/npm/sync-packages.mjs
3. commit and push
4. create and push a matching git tag like v0.1.0
5. let GitHub Actions publish the platform packages first, then the main maleme package

Local validation on the current machine:

node scripts/npm/sync-packages.mjs
cargo build --release
node scripts/npm/stage-binary.mjs aarch64-apple-darwin target/release/maleme
npm pack ./npm/platforms/darwin-arm64
npm pack ./npm/main

Repository Metadata

• Source: github.com/Yeuoly/maleme
• Primary language: Rust
• License: WTFPL
• Distribution model: local executable and npm-distributed native binary

Star History

Scope

This repository is intentionally local, explicit, and file-oriented. It is not intended to be a hosted analytics platform, a moderation service, or a generalized telemetry pipeline.

License

This project is distributed under the terms of the WTFPL.