io.github.yifanyifan897645/git-summary
NPM · GIT-SUMMARY-MCP · SCANNED AUG 3
Git repo intelligence: summaries, blame, changelogs, branch health, and history search
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 101 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 536 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · git-summary-mcp
claude mcp add yifanyifan897645-git-summary -- npx -y git-summary-mcp
codex mcp add yifanyifan897645-git-summary -- npx -y git-summary-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"yifanyifan897645-git-summary": {
"type": "local",
"command": [
"npx",
"-y",
"git-summary-mcp"
],
"enabled": true
}
}
} openclaw mcp add yifanyifan897645-git-summary --command npx --arg -y --arg git-summary-mcp
mcp_servers:
yifanyifan897645-git-summary:
command: "npx"
args: ["-y", "git-summary-mcp"] {
"mcpServers": {
"yifanyifan897645-git-summary": {
"command": "npx",
"args": [
"-y",
"git-summary-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +61
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 99 packages
99 packages in the resolved dependency tree · 99 deprecated · 31 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
git_blame ~104
Analyze who wrote each line of a file, when, and in which commit. Get top contributors and ownership breakdown. Optionally limit to a line range.
| Name | Type | Req | Description |
|---|---|---|---|
| end_line | number | — | End line number (optional, for partial blame) |
| file | string | yes | File path relative to repo root |
| repo_path | string | — | Path to the Git repository (defaults to cwd) |
| start_line | number | — | Start line number (optional, for partial blame) |
No output schema declared.
No examples provided.
git_branch_health ~55
Analyze all local branches: find stale branches, merged branches ready for cleanup, and branches that are ahead/behind. Helps keep your repo tidy.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_path | string | — | Path to the Git repository (defaults to cwd) |
No output schema declared.
No examples provided.
git_changelog ~105
Auto-generate a changelog from Git commits. Groups commits by type (feat, fix, docs, etc.) using conventional commit format. Specify a range or get the full log.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | — | Start commit/tag (e.g. 'v1.0.0') |
| repo_path | string | — | Path to the Git repository (defaults to cwd) |
| to | string | — | End commit/tag (e.g. 'v2.0.0') |
No output schema declared.
No examples provided.
git_changes ~107
Get a summary of changes in a commit range: what files changed, who changed them, and a diff stat. Useful for understanding what happened between two points in history.
| Name | Type | Req | Description |
|---|---|---|---|
| max_commits | number | — | Max commits to analyze (default 30) |
| range | string | — | Git commit range, e.g. 'main..feature' or 'HEAD~5..HEAD' or a tag range |
| repo_path | string | — | Path to the Git repository (defaults to cwd) |
No output schema declared.
No examples provided.
git_search ~92
Search through Git history for commits matching a query. Searches both commit messages and code changes (pickaxe search). Find when a change was introduced or a bug was created.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | — | Maximum results to return (default 20) |
| query | string | yes | Search term to find in commit messages or code changes |
| repo_path | string | — | Path to the Git repository (defaults to cwd) |
No output schema declared.
No examples provided.
git_summary ~73
Get a structured overview of a Git repository: current branch, recent commits, contributors, and repo stats. Works on any local Git repo.
| Name | Type | Req | Description |
|---|---|---|---|
| commit_count | number | — | Number of recent commits to include (default 20) |
| repo_path | string | — | Path to the Git repository (defaults to current working directory) |
No output schema declared.
No examples provided.