io.github.promptwheel-ai/logbook
NPM · @PROMPTWHEEL/LOGBOOK-MCP · SCANNED AUG 3
Local Git-history memory for coding agents: reverts, suppressions, hotspots, and annotations.
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 (96 of 100), 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 (96 of 100), 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 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 594 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
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 · @promptwheel/logbook-mcp
claude mcp add promptwheel-ai-logbook -- npx -y @promptwheel/logbook-mcp
codex mcp add promptwheel-ai-logbook -- npx -y @promptwheel/logbook-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"promptwheel-ai-logbook": {
"type": "local",
"command": [
"npx",
"-y",
"@promptwheel/logbook-mcp"
],
"enabled": true
}
}
} openclaw mcp add promptwheel-ai-logbook --command npx --arg -y --arg @promptwheel/logbook-mcp
mcp_servers:
promptwheel-ai-logbook:
command: "npx"
args: ["-y", "@promptwheel/logbook-mcp"] {
"mcpServers": {
"promptwheel-ai-logbook": {
"command": "npx",
"args": [
"-y",
"@promptwheel/logbook-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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +60
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −22
- 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 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 45
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/@promptwheel/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 96 packages
96 packages in the resolved dependency tree · 95 deprecated · 29 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.
logbook_annotate ~131
Persist WHY a commit happened (lazy enrichment). When you investigate a do-not-retry revert or a suppression — its failure mode, its cause — save the finding so the next session gets it for free instead of re-investigating. Judgments, not records: attributed and dated.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | — | who inferred it (model/agent name) |
| repo | string | yes | absolute path to the git repository |
| sha | string | yes | the commit being explained (any unique prefix) |
| why | string | yes | the inferred cause, one sentence, specific (max 400 chars) |
No output schema declared.
No examples provided.
logbook_audit ~67
What is STILL suppressed in HEAD and since when (blame-dated), with re-silencing fight logs. Use when asked what tests are skipped, what debt is live, or whether a suppression keeps coming back.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | absolute path to the git repository |
No output schema declared.
No examples provided.
logbook_context ~162
Return the same filtered history order as logbook_query in compact, bounded pages for agent context. This is deterministic delivery, not relevance ranking. Follow NEXT cursors until END complete when completeness matters.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | — | opaque NEXT cursor from the previous page; rejects stale or changed queries |
| downgrade | number | — | min assertion downgrades |
| file | string | — | substring match against files touched |
| grep | string | — | substring match against commit subject |
| repo | string | yes | absolute path to the git repository |
| revert | boolean | — | — |
| since | string | — | — |
| suppress | boolean | — | only events that added suppressions |
| until | string | — | — |
| weaken | number | — | min net assertions removed |
No output schema declared.
No examples provided.
logbook_digest ~77
The repo's history digest: hotspots, do-not-retry reverts, suppression ledger, fragile areas, notable events, per-file history. Use when starting work in an unfamiliar repo, before a refactor or large change, or when deciding whether green tests can be trusted.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | absolute path to the git repository |
No output schema declared.
No examples provided.
logbook_query ~157
Filter the full commit-event record with precision. Start with file + event type (for example file and revert) before broad grep. Returns up to `limit` matches, default 100, with exact counts and explicit truncation recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| downgrade | number | — | min assertion downgrades |
| file | string | — | substring match against files touched |
| grep | string | — | substring match against commit subject |
| limit | integer | — | — |
| repo | string | yes | absolute path to the git repository |
| revert | boolean | — | — |
| since | string | — | — |
| suppress | boolean | — | only events that added suppressions |
| until | string | — | — |
| weaken | number | — | min net assertions removed |
No output schema declared.
No examples provided.