# @pasichdev/docket

One list every AI tool you use can write to — scoped per project, local-first, self-hostable.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 3.0.0
- **Author:** io.github.pasichDev
- **License:** MIT
- **npm:** @pasichdev/docket
- **Source:** https://github.com/pasichDev/docket
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 17 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-06T23:50:49.955Z
- **Version scanned:** 3.0.0
- **CVEs:** none found by OSV at scan time

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `todo_add` — Capture work the moment it comes up, from any tool or project, without the ceremony of a ticket. Automatically filed under the current project — you never need 
- `todo_edit` — Edit an existing item's title/description/category/priority/dueDate/sourceUrl/list by id. Only fields you pass are changed. Pass an empty string ("") for descri
- `todo_claim` — Mark an item as actively being worked on by you (the calling agent). Advisory, not a lock — check todo_list(inProgress: true) before starting new work to avoid 
- `todo_release` — Clear the in-progress claim on an item without completing it (e.g. you're pausing this work).
- `todo_list` — What's open here. Scoped to the current project (plus unfiled items) unless you ask otherwise, and compact by default — one line per item. Pass workspace:"*" to
- `todo_complete` — Mark a todo as done by id.
- `todo_history` — Show the change history (create/edit/claim/release/complete) for one item, who made each change and when.
- `todo_version` — Report this docket process's data format version and start time. Use to sanity-check whether your MCP connection is running stale code (e.g. right after an upda
- `todo_check_update` — Check whether a newer version of docket is published on npm. Read-only — never installs anything. If one is available, tell the user and let THEM decide whether
- `todo_delete` — Permanently remove a todo by id.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"docket\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@pasichdev/docket\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 37, ceiling 61 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40pasichdev%2Fdocket
- Install plan: https://forgeregistry.com/api/v1/packages/%40pasichdev%2Fdocket/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40pasichdev%2Fdocket
- HTML page: https://forgeregistry.com/registry/%40pasichdev%2Fdocket
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.