GitPin

NPM · GITPIN · SCANNED AUG 3

Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.

Available components

74 74 Trust /100

Trust breakdown (6 categories)

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 (100 of 104), 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 (100 of 104), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency97

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Cryptographically verified build provenance (signed, bound to shmindmaster/gitpin). View diagnostics → Pass
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 1 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability75

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (fair).Partial
Tool/resource definitions use about 658 tokens (~50/item across 13 items; 12 tools + 1 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management10

Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage67

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
0% of tool parameters carry a description.Fail

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

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 · gitpin

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add shmindmaster-gitpin -- npx -y gitpin

# add to Codex CLI

codex mcp add shmindmaster-gitpin -- npx -y gitpin

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shmindmaster-gitpin": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "gitpin"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add shmindmaster-gitpin --command npx --arg -y --arg gitpin

# ~/.hermes/config.yaml

mcp_servers:
  shmindmaster-gitpin:
    command: "npx"
    args: ["-y", "gitpin"]

// mcp.json

{
  "mcpServers": {
    "shmindmaster-gitpin": {
      "command": "npx",
      "args": [
        "-y",
        "gitpin"
      ]
    }
  }
}

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 +50
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: shmindmaster/gitpin security
- Stability: unverified → 0.07 ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → fair ▲ functional
- License: unverified → pass ▲ functional
- Licence: MIT functional
1 Aug 26 −11
- Provenance: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Known CVEs: partial → unverified ▼ security
- The attested source repository moved: shmindmaster/gitpin security
- License: pass → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: unverified functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 0 functional
- Licence: MIT functional
- Package version: 0.6.0 → 0.6.2 functional
31 Jul 26 34

First indexed and scored.

Show 1 earlier entry Hide earlier entries

Diagnostics

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 verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:: shmindmaster/gitpin
Certificate issuer:: https://token.actions.githubusercontent.com
Certificate SAN:: https://github.com/shmindmaster/gitpin/.github/workflows/release.yml@refs/tags/v0.6.2
Rekor log index:: 2313560623
Predicate type:: https://slsa.dev/provenance/v1
Subject digest:: sha512:6f02d9c34ffeadc2ad120755e906c272a363feae2dc1f8a11a4315182253e234c5a3216fcdc3a67f52753389b0003d7e03b0f3a53ad3dcfb514cd836c
Discovery method:: attestation_endpoint

Dependencies 100 packages

100 packages in the resolved dependency tree · 100 deprecated · 31 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 12 exposed · ~643 tokens

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.

Tool Tokens

pin.analyze ~34

EvidenceBrief (knownFacts/gaps/evidenceSetId), documentation gaps, or coverage compare. Decision evidence—not a dump.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pin.catalog ~43

Call first to discover registered Git roots (HEAD SHAs, doc counts, stale). Not a content claim. Use before search/prove.

Input Output Examples

Name	Type	Req	Description
view	string	—	—

No output schema declared.

No examples provided.

pin.compare ~47

Diff changed paths between two hex revisions. Bounded change evidence for reviews—not semantic search.

Input Output Examples

Name	Type	Req	Description
base	string	yes	—
head	string	yes	—
repository	string	yes	—

No output schema declared.

No examples provided.

pin.get_doc ~45

Read one committed documentation page as a pinned evidence slice with full SHA. Prefer pin.prove for claims.

Input Output Examples

Name	Type	Req	Description
repository	string	yes	—
sourcePath	string	yes	—

No output schema declared.

No examples provided.

pin.inspect ~53

Inspect HEAD-pinned status, commits, manifests, tests, or recent changes. status shows dirty work excluded from evidence.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	—
operation	string	yes	—
repository	string	yes	—

No output schema declared.

No examples provided.

pin.prove ~80

Primary product tool: one-path evidence pack (slice, path, line, full SHA, content hash, handle, verify next-step). Prefer for every factual claim.

Input Output Examples

Name	Type	Req	Description
claim	string	—	—
lineEnd	integer	—	—
lineStart	integer	—	—
repository	string	yes	—
sourcePath	string	yes	—

No output schema declared.

No examples provided.

pin.prove_set ~47

Multi-cite evidence set (1–8 paths, multi-repo OK). Use when an answer needs several citations. Next: pin.verify_set.

Input Output Examples

Name	Type	Req	Description
items	array	yes	—

No output schema declared.

No examples provided.

pin.read ~66

Read a HEAD-only source slice (path, lines, full SHA). Sensitive paths blocked. Prefer pin.prove when making a claim.

Input Output Examples

Name	Type	Req	Description
lineEnd	integer	—	—
lineStart	integer	—	—
repository	string	yes	—
sourcePath	string	yes	—

No output schema declared.

No examples provided.

pin.search_code ~53

Find code candidates via git grep at HEAD. Never treat hits as final claims—pin.prove then pin.verify (or prove_set/verify_set).

Input Output Examples

Name	Type	Req	Description
query	string	yes	—
repository	string	yes	—

No output schema declared.

No examples provided.

pin.search_docs ~48

Find documentation candidates (not claims). Before any factual assertion call pin.prove or pin.prove_set, then pin.verify.

Input Output Examples

Name	Type	Req	Description
query	string	yes	—
repository	string	—	—

No output schema declared.

No examples provided.

pin.verify ~74

Close the prove loop: re-check path@SHA with git show; optional mustContain for claim-text. Reports HEAD match and claimVerdict.

Input Output Examples

Name	Type	Req	Description
line	integer	—	—
mustContain	string	—	—
repository	string	yes	—
sha	string	yes	—
sourcePath	string	yes	—

No output schema declared.

No examples provided.

pin.verify_set ~53

Batch re-check up to 8 citations (from pin.prove_set or a pack). For multi-repo answers and CI citation gates.

Input Output Examples

Name	Type	Req	Description
evidenceSetId	string	—	—
items	array	yes	—

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

31 Jul 3 Aug