io.github.cxk280/locksmith
NPM · LOCKSMITH-MCP · SCANNED AUG 3
Lints PostgreSQL migrations for dangerous locking operations and suggests safe rewrites.
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 (103 of 107), 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 (103 of 107), 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 34 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 211 tokens (~52/item across 4 items; 2 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · locksmith-mcp
claude mcp add cxk280-locksmith -- npx -y locksmith-mcp
codex mcp add cxk280-locksmith -- npx -y locksmith-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cxk280-locksmith": {
"type": "local",
"command": [
"npx",
"-y",
"locksmith-mcp"
],
"enabled": true
}
}
} openclaw mcp add cxk280-locksmith --command npx --arg -y --arg locksmith-mcp
mcp_servers:
cxk280-locksmith:
command: "npx"
args: ["-y", "locksmith-mcp"] {
"mcpServers": {
"cxk280-locksmith": {
"command": "npx",
"args": [
"-y",
"locksmith-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.
- 3 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.27 ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 2 Aug 26 +36
- Malware scan: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 1 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −47
- Malware scan: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Jul 26 +29
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −29
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 27 Jul 26 53
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 103 packages
103 packages in the resolved dependency tree · 103 deprecated · 33 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.
analyze_migration Analyze a SQL migration for locking hazards ~112
Lint a PostgreSQL migration for operations that take dangerous locks (table rewrites, blocking index builds, validating constraints, destructive/breaking changes) and return a PASS/REVIEW/BLOCK verdict with per-statement findings and safe rewrites. Call this before applying or approving any migration.
| Name | Type | Req | Description |
|---|---|---|---|
| assumeLargeTables | boolean | — | Assume target tables are large/hot, so scans and rewrites are flagged. Default true (fail safe). |
| sql | string | yes | The full SQL migration script to analyze. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | — |
| stats | object | yes | — |
| summary | string | yes | — |
| verdict | string | yes | — |
No examples provided.
explain_lock Explain a PostgreSQL lock mode ~66
Given a lock mode name (e.g. 'ACCESS EXCLUSIVE') or a fragment of an operation, explain what it blocks and which operations acquire it.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A lock mode name or operation fragment, e.g. 'ACCESS EXCLUSIVE' or 'create index'. |
No output schema declared.
No examples provided.