FlyDocs

NPM · @FLYDOCS/CLI · SCANNED AUG 21

Spec-driven development workflow for AI agents: issue lifecycle, sessions, project updates.

Available components

59 59 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 Security98

No malware found by supply-chain analysis.Pass
No known CVEs affecting this package version or its production dependencies.Pass
No install/post-install scripts declared.Pass
25 of 60 dependencies flagged as unhealthy. View diagnostics → Partial

Provenance & Transparency6

Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: no license is declared. See how to fix → Fail
Actively maintained (last published 0 days ago).Pass
Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified

Schema Quality & AI Usability72

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 1365 tokens (~124/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management0

Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified

Tool Coverage88

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
59% of tool parameters carry a description.Partial
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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 · @flydocs/cli

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add ai-flydocs-flydocs -- npx -y @flydocs/cli

# add to Codex CLI

codex mcp add ai-flydocs-flydocs -- npx -y @flydocs/cli

// opencode.json

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

# add to OpenClaw

openclaw mcp add ai-flydocs-flydocs --command npx --arg -y --arg @flydocs/cli

# ~/.hermes/config.yaml

mcp_servers:
  ai-flydocs-flydocs:
    command: "npx"
    args: ["-y", "@flydocs/cli"]

// mcp.json

{
  "mcpServers": {
    "ai-flydocs-flydocs": {
      "command": "npx",
      "args": [
        "-y",
        "@flydocs/cli"
      ]
    }
  }
}

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.

20 Aug 26 +15
- Malware scan: unverified → pass ▲ security
19 Aug 26 44

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 21 Aug 2026 · Analysed npm/@flydocs/cli@1.3.8

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	npm

Dependencies 60 packages

Packages resolved	60
Stale	25
Tree resolution	Complete

MCP tools · 11 exposed · ~1,231 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

change_context Change Context ~133

See what an issue shipped: its pull requests, linked issues and decisions, each claim citing its source.

Input Output Examples

Name	Type	Req	Description
limit	integer	–	Per-section cap: pull requests, related issues, decisions
mode	string	–	shipped: what the issue records. impact: blast radius (not yet)
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.
target	string	yes	Issue reference, e.g. FLY-123. A module or topic string is accepted by the schema and answered with NOT_AVAILABLE until the graph lands

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_acceptance_update Update Acceptance Criteria ~89

Check, uncheck, defer or annotate acceptance criteria by id. Never rewrite the description to do this. See stages/implement.md.

Input Output Examples

Name	Type	Req	Description
changes	array	yes	–
ref	string	yes	Issue reference, e.g. FLY-123
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_activate Activate Issue ~121

Assign, transition and record session state in one call. Not transactional; re-running is safe. Procedure: stages/activate.md.

Input Output Examples

Name	Type	Req	Description
assignee	string	yes	Provider id, or 'me'
comment	string	yes	Why the work is starting — the transition requires it
ref	string	yes	Issue reference, e.g. FLY-123
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.
status	string	–	Defaults to IMPLEMENTING

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_comment Comment on Issue ~72

Post a comment. Templates: reference/comment-templates.md.

Input Output Examples

Name	Type	Req	Description
body	string	yes	–
ref	string	yes	Issue reference, e.g. FLY-123
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_create Create Issue ~171

Capture a new issue. Procedure: stages/capture.md.

Input Output Examples

Name	Type	Req	Description
assignee	string	–	Provider id, or 'me'
description	string	–	Required unless triage is true
estimate	integer	–	Estimate points on the provider scale — `flydocs run workspace.get-estimate-scale` reports it. See reference/priority-estimates.md
milestone	string	–	–
priority	integer	–	0 none, 1 urgent, 2 high, 3 medium, 4 low
project	string	–	–
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.
title	string	yes	–
triage	boolean	–	–
type	string	yes	–

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_get Get Issue ~78

Read one issue with its status, description, and acceptance criteria. Read before you write.

Input Output Examples

Name	Type	Req	Description
fields	string	–	–
ref	string	yes	Issue reference, e.g. FLY-123
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_list List Issues ~149

List issues in the current focus — active sprint, board, or your assigned work.

Input Output Examples

Name	Type	Req	Description
active	boolean	–	–
all	boolean	–	Bypass the product scope cascade
assignee	string	–	–
board	string	–	Board id, or 'active'
focused	boolean	–	–
limit	integer	–	–
milestone	string	–	–
mine	boolean	–	–
project	string	–	–
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.
sprint	string	–	Sprint id, or 'active'
status	string	–	–

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

issue_transition Transition Issue ~152

Move an issue to a canonical status. The comment is required and templated: reference/comment-templates.md, reference/status-workflow.md.

Input Output Examples

Name	Type	Req	Description
comment	string	yes	Never optional — no status moves silently
force	string	–	Provider-native override for STATUS_NOT_REACHABLE
ref	string	yes	Issue reference, e.g. FLY-123
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.
status	string	yes	Canonical FlyDocs status: BACKLOG, READY, IMPLEMENTING, BLOCKED, REVIEW, TESTING, COMPLETE, ARCHIVED, CANCELED, DUPLICATE

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

project_update Post Project Update ~78

Post a mid-session project health update; end-of-session updates belong to session_wrap. See session.md.

Input Output Examples

Name	Type	Req	Description
body	string	yes	–
health	string	yes	–
project	string	–	–
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

session_start Start Session ~61

Load continuity: the active issue with AC progress, last session's summary, pending work and blockers. Procedure: session.md.

Input Output Examples

Name	Type	Req	Description
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.

Name	Type	Req	Description
ok	boolean	yes	–

No examples provided.

session_wrap Wrap Session ~127

End the session: write the handoff summary and post the project update from the filled wrap template. Procedure: session.md.

Input Output Examples

Name	Type	Req	Description
blockers	array	–	–
body	string	–	Filled session-wrap template; sections are enforced
health	string	–	Omit to wrap without posting a project update
issues	array	–	–
notes	string	–	–
pending	array	–	–
project	string	–	–
repo	string	–	Workspace repo to target. Defaults to the current repo, or the first repo at a multi-repo root.

Name	Type	Req	Description
ok	boolean	yes	–

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

19 Aug 21 Aug