@nxuss/lemma weekly downloads statistics
By nxuss · npm · Claude Code
Intelligent AI Gateway for IDEs & Agents — Semantic cache, Privacy Firewall, Infrastructure Command Center, and Autonomous Cost-Optimization.
@nxuss/lemma has 1,283 recorded weekly downloads on npm, a decrease of 35.8% over the past 30 days.
It ranks #1347 of 2,251 tracked npm listings by weekly downloads.
Over 90 days, weekly downloads changed by +36.9%.
PluginStats has 121 daily observations since Jun 19, 2026; the latest is from Oct 17, 2026.
About @nxuss/lemma
🧠 Lemma
The Intelligent local-first AI Gateway — Privacy, Performance, Static Code Intelligence, and Infrastructure Command Center for the Agentic Era.
Lemma sits between your development environment and LLM providers as an MCP server / local proxy. It cuts what actually enters the model's context — repeated reads, unfiltered command output, tool schemas the project can't use — while keeping every answer verifiable: a cache hit is disclosed as a cache hit, a compressed file is never what the user sees, and a savings number always traces back to an auditable ledger, never an estimate.
🚀 Quick start
Muse — no setup needed. This repo is already Muse-compatible zero-config: clone and open with muse — the skill at .agents/skills/lemma/SKILL.md auto-loads and lemma call works via bash. See MCP integration.
🆕 v1.22.0 — Lemma auto-activates in every LLM client. npm i -g @nxuss/lemma registers the skill in your user catalog (auto-loads in every muse session, any project) and lemma init wires each project for Muse, Claude Code, Cursor, Codex, Windsurf, Kiro and OpenCode. Health check: lemma doctor.
🆕 v1.33.0 — C# (.NET) support, honestly labeled. New per-project language detection (.csproj/.sln, target frameworks, mixed repos) and a read-only capability_matrix tool so clients stop guessing what works outside TypeScript. get_ast_hologram and get_symbol_surgical_context now serve C# (zero-dependency parser), depgraph gives using-based graphs with explicit unresolved externals, and validate_patch_sandbox runs dotnet build on a temp project copy — or says `NOT a build when there's no SDK. refactor, surgical_ast_insert, type_coverage_report, entropy_score` and affected_tests return support level: fallback on C# targets instead of faking it: nothing is modified. No new runtime dependencies. See the changelog.
🆕 v1.32.0 — what a command can see and reach. run_workspace_command no longer hands the child the host's whole environment (tokens, API keys, the license key): it gets a short allowlist, extendable via mcp.commandEnv.allow. cat, ls, grep, find, sed… must keep their paths inside the workspace, and on Windows a backslash executable path no longer passes as a bare name. New and opt-in: mcp.sandbox.mode: "docker" runs each command in a throwaway container with only the workspace, no network, no host environment and a read-only root, and fails closed if Docker is unavailable. Behavior change: a command that relied on an inherited variable now needs it allowed by name (or mcp.commandEnv.mode: "inherit"). Also fixed: options a tool advertised and ignored (generate_pr_workflow.autoApprove, jenkins_generate_pipeline, TaskLifecycle.cleanup), now guarded by a test. See the changelog.
🆕 v1.31.1 — secrets, symlinks and stale fixes. A second round of dogfooding (rounds 11-20) found that run_workspace_command handed .env secrets to the model in clear (cat .env, grep -r PASSWORD .) while read_workspace_file masked them — command output is now scrubbed too. Also closed: writes escaping the workspace through a dangling symlink, an allowlist that accepted ./git and env sh -c, a compressor that cut code at // inside strings, a scrubber that masked code as secrets, brain_trash purge wiping the whole trash on an invalid olderThanDays, and local_semantic_autofix presenting a stale fix as a clean zero-token hit (it now says STALE, or that the fix is not anchored to any file). Patches keep your CRLF line endings and tab/space indentation, and list_workspace_dir caps huge directories. See the changelog.
🆕 v1.31.0 — tools that said "success" without doing the job, fixed. Dogfooding with a small project driven only through Lemma's own tools found a pattern: several tools answered cleanly without having done what was asked. validate_patch_sandbox approved *every* patch (it ran npx tsc in an empty temp dir, which resolves a different package); surgical_ast_insert ignored an unknown parameter, appended code outside the class and reported success (it now refuses syntax-breaking patches); get_ast_hologram ignored filePath and scanned the whole repo (212K chars); search_workspace could not find its own source file (two stray NUL bytes made it look binary). Also fixed: type_coverage_report counting inferred types as missing, affected_tests using the root runner for nested packages, lockfiles and changelogs ranking as "risk 100" in git_heatmap_risk / precrime_static, review_diff flagging missing tests that already exist, and brain_export being annotated read-only while it writes a file. New: every result now says when an argument was ignored (`⚠️ Lemma ignored unknown argument … Valid: …`, also on failures), and when a newer build exists than the running MCP process — a rebuild never reaches a process that is already running, so reconnect it (Claude Code: /mcp → lemma). get_symbol_surgical_context now resolves methods (Class.method). Behavior change: the extra "Proceed?" confirmation on run_workspace_command, apply_workspace_patch and forget_memory is now off by default (the allowlist and path checks are unchanged); set "mcp": { "confirmActions": true } in lemma.config.json to get it back.
**🆕 v1.30.1 — lemma init now really installs the Brain's hooks, and big search results stop eating your context.** Dogfooding found that lemma init finished "successfully" without installing the git hooks (post-commit, post-merge, post-checkout) or the Claude Code / Codex / Cursor / OpenCode tool hooks that v1.28–v1.30 advertised — so commits never became memories. Fixed (idempotent, merge-only, --no-hooks to skip); re-run lemma init after updating. search_workspace also had a match cap but no size cap: one hit inside a minified bundle returned the whole line (~75k tokens reproduced). Lines are now a 240-char window around the hit and the result is capped at ~8k tokens, with what was dropped disclosed. Plus 10% smaller tool schemas (−938 tokens per session).…
Description from the npm listing.
- semantic-cache
- privacy-firewall
- ai-security
- cost-optimization
- intelligent-proxy
- ai-agents
- orchestration
- ide-sync
- llm-gateway
- openai-proxy
- anthropic-proxy
- vector-database
- muse
- muse-code
- muse-spark
- claude-code
- cursor
- codex
Where @nxuss/lemma sits in the listing
Each band is one page of 20. Weekly downloads on a log scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (121)Similar npm Claude Code plugins
Data source
Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.
Listing: https://www.npmjs.com/package/@nxuss/lemma. First seen Oct 16, 2026; last successful collection Oct 18, 2026. See the methodology.