Is Sigmap safe and trustworthy?

tashan scores Sigmap on public evidence — tashan score 64.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Sigmap?

In Claude Code: run `claude mcp add sigmap -- npx -y sigmap`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Sigmap

npm

The deterministic, verifiable grounding layer for AI code work — a zero-dependency signature-and-evidence map that grounds Claude, Cursor, Copilot, Aider, Windsurf, local LLMs & MCP agents against your real code (repo + installed libraries) so they stop h

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Code review

Who it is for: Software engineer

Install (Claude Code):

claude mcp add sigmap -- npx -y sigmap

solid

“10 worked examples; short of deep on per-tool docs and a stated limitation; read with 1 linked doc(s)”

This grade is wrong ›

tashan score: 64.0
Instruction depth: 66.0 (solid — documents the job properly, with examples you could follow)
Adoption: 703/wk
Upkeep: 71.0
Freshness: 92.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 8.32.0 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

Signed build provenancepublished from public CI with an attestation

What changed recently

2026-08-24 the tashan score for sigmap rose to 71.0, from 64.0 Upkeep, freshness or adoption moved enough to change how this measures.
2026-08-27 sigmap published 8.28.1, was 8.28.0 A new release is available.
2026-09-13 the tashan score for sigmap fell to 64.0, from 70.0 Upkeep, freshness or adoption moved enough to change how this measures.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 4 changes to Sigmap in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-sigmap.svg)](https://tashan.sh/capability/pkg-sigmap.html)

npm ↗ · source ↗ · pkg:sigmap

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?