New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

@didwork/inspect

Package Overview
Dependencies
Maintainers
1
Versions
5
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@didwork/inspect

DidWork Capability Trust — static inspection of what agent tools can actually affect, with evidence.

npmnpm
Version
0.0.1
Version published
Weekly downloads
233
429.55%
Maintainers
1
Weekly downloads
 
Created
Source

@didwork/inspect

Capability Trust for agent tools: what can this tool actually affect, and what evidence does DidWork have for saying so?

import { inspectProject } from "@didwork/inspect";

const { tools, summary } = inspectProject({ root: "." });

Each tool gets a CapabilityProfile (types in @didwork/sdk) with three blocks kept apart on purpose: declared (from did.tool({ effects })), evidenced (source-level evidence and the gaps analysis could not close), and observed (runtime; always null in this release).

  • risk is the highest evidenced consequence; confidence is the strength of the evidence. They are separate. unknown never degrades to low.
  • status is failed when evidence exceeds the declaration (DECLARATION_MISMATCH), unknown when analysis could not establish the profile (INSUFFICIENT_EVIDENCE, IMPLEMENTATION_UNAVAILABLE), and verified only when the profile is established.

Supported today: TypeScript/JavaScript projects registering tools with @modelcontextprotocol/sdk (server.tool, server.registerTool) or declaring them with did.tool(...). Other languages produce no tools rather than guesses. Analysis runs locally and reads source; nothing is uploaded.

The evidence table lives in src/signatures.ts. Add a row per package call; catch-all rows take the riskier reading.

Keywords

mcp

FAQs

Package last updated on 05 Sep 2026

Related posts