Is Project Knowledge safe and trustworthy?

tashan scores Project Knowledge on public evidence — tashan score 56.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: shell. 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 Project Knowledge?

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

Who maintains Project Knowledge?

source: SanQianX/project-knowledge-base.

‹ The Index

Project Knowledge

npm

Knowledge base manager with Git integration, AI-driven analysis, and bilingual (zh-CN/en-US) knowledge output

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: Knowledge management · Version control

Who it is for: Operations · Researcher · Software engineer

Install (Claude Code):

claude mcp add project-knowledge -- npx -y project-knowledge

solid

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

This grade is wrong ›

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

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 4.1.22

Runs shell commandsfrom declared dependencies

Signed build provenancepublished from public CI with an attestation

What changed recently

2026-08-11 project-knowledge now reaches shell Its declared dependencies reach further into your machine than they did before.

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 1 change to Project Knowledge 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.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your 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-project-knowledge.svg)](https://tashan.sh/capability/pkg-project-knowledge.html)

npm ↗ · source ↗ · pkg:project-knowledge

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?