io.github.nakishiyaman/dig

MCPattested
v0.4.1io.github.nakishiyamanUnknownUpdated 6mo agonpmGitHub

MCP server for code archaeology: git blame, file history, contributors, and co-change analysis

MCP server for AI-powered code archaeology — explore git blame, file history, contributor patterns, and co-change analysis through the Model Context Protocol. ------|-------------| | PR review briefing with risk flags, reviewer suggestions, and missing file detection | | Code archaeology narrative — explains why code exists by combining blame, commits, contributors, and co-changes |…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
6mo agoLast update
Package
Authorio.github.nakishiyaman
LicenseUnknown
Version0.4.1
Sourcemcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · d92598f
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface40 tools · none privileged
Security scan✓ Cleanv0.40.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

40 tools · none privileged
Statically extracted from the published packagev0.40.0 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

git_activity_droughtNo description published

This tool published no description. Forge does not invent one.

git_author_timelineNo description published

This tool published no description. Forge does not invent one.

git_bisect_guideNo description published

This tool published no description. Forge does not invent one.

git_blame_contextNo description published

This tool published no description. Forge does not invent one.

git_branch_activityNo description published

This tool published no description. Forge does not invent one.

git_cherry_pick_detectNo description published

This tool published no description. Forge does not invent one.

git_code_ageNo description published

This tool published no description. Forge does not invent one.

git_code_churnNo description published

This tool published no description. Forge does not invent one.

git_code_ownership_changesNo description published

This tool published no description. Forge does not invent one.

git_commit_clusterNo description published

This tool published no description. Forge does not invent one.

git_commit_frequencyNo description published

This tool published no description. Forge does not invent one.

git_commit_graphNo description published

This tool published no description. Forge does not invent one.

git_commit_message_qualityNo description published

This tool published no description. Forge does not invent one.

git_commit_patternsNo description published

This tool published no description. Forge does not invent one.

git_commit_showNo description published

This tool published no description. Forge does not invent one.

git_complexity_hotspotsNo description published

This tool published no description. Forge does not invent one.

git_conflict_historyNo description published

This tool published no description. Forge does not invent one.

git_contributor_growthNo description published

This tool published no description. Forge does not invent one.

git_contributor_networkNo description published

This tool published no description. Forge does not invent one.

git_contributor_patternsNo description published

This tool published no description. Forge does not invent one.

git_coordination_bottleneckNo description published

This tool published no description. Forge does not invent one.

git_dependency_mapNo description published

This tool published no description. Forge does not invent one.

git_diff_contextNo description published

This tool published no description. Forge does not invent one.

git_expertise_decayNo description published

This tool published no description. Forge does not invent one.

git_file_historyNo description published

This tool published no description. Forge does not invent one.

git_file_risk_profileNo description published

This tool published no description. Forge does not invent one.

git_hotspotsNo description published

This tool published no description. Forge does not invent one.

git_impact_analysisNo description published

This tool published no description. Forge does not invent one.

git_knowledge_loss_riskNo description published

This tool published no description. Forge does not invent one.

git_knowledge_mapNo description published

This tool published no description. Forge does not invent one.

git_line_historyNo description published

This tool published no description. Forge does not invent one.

git_merge_baseNo description published

This tool published no description. Forge does not invent one.

git_merge_timelineNo description published

This tool published no description. Forge does not invent one.

git_offboarding_simulationNo description published

This tool published no description. Forge does not invent one.

git_pickaxeNo description published

This tool published no description. Forge does not invent one.

git_refactor_candidatesNo description published

This tool published no description. Forge does not invent one.

git_reflog_analysisNo description published

This tool published no description. Forge does not invent one.

git_related_changesNo description published

This tool published no description. Forge does not invent one.

git_release_comparisonNo description published

This tool published no description. Forge does not invent one.

git_release_notesNo description published

This tool published no description. Forge does not invent one.

0 of 40 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for AI-powered code archaeology — explore git blame, file history, contributor patterns, and co-change analysis through the Model Context Protocol. ------|-------------| | PR review briefing with risk flags, reviewer suggestions, and missing file detection | | Code archaeology narrative — explains why code exists by combining blame, commits, contributors, and co-changes | ------|-------------| | Multi-dimensional risk assessment for a single file | | Repository-wide health summary |…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.