Discussions · Contributing · Changelog · Issues
You shipped a TypeScript AI agent. Do you know every function it can call that writes to a database, sends an email, charges a card, or deletes data — and which ones have zero checks?
diplomat-agent-ts runs a static AST scan and tells you exactly that. Two dependencies. ~9 s on a 7,874-file TypeScript agent codebase (OpenClaw, M-series). ~30 s on slower x86 hardware without a tsconfig.json.
npm install -D @diplomat-ai/diplomat-agent-ts
npx diplomat-agent-ts scan . # scan from project root
npx diplomat-agent-ts scan ./src # or a specific subdirectoryIn a web app, a human clicks a button. The UI has validation, confirmation dialogs, rate limits per session.
In an agent, an LLM decides which functions to call, with what arguments, how many times. It doesn't know your business rules. It can loop, hallucinate arguments, or get prompt-injected.
Without guards in the code, there's nothing between the LLM's decision and the real-world consequence.
We scanned the OpenClaw agent codebase at pinned commit 49d9996d (7,874 TypeScript files, ~9 s on M-series, ~30 s on x86). 419 tool calls had real side effects. 332 of them (79%) had zero checks. Not a single one was confirmed.
40+ patterns across 12 side-effect categories:
| Category | Examples (TS-native) | Required guards |
|---|---|---|
payment |
stripe.charges.create(), stripe.refunds.create() |
bounds, rate limit, approval |
database_write |
Prisma .create() / .update(), Mongoose .save() |
input validation, rate limit |
database_delete |
Prisma .delete(), Mongoose .deleteOne(), raw DELETE |
batch protection, confirmation |
http_write |
axios.post(), fetch(POST), got.put() |
rate limit, retry bound |
email |
nodemailer.sendMail(), resend.emails.send(), sgMail.send() |
rate limit |
messaging |
twilio.messages.create(), slack.chat.postMessage() |
rate limit |
agent_invocation |
agent.run(), graph.invoke(), Runner.run() |
input validation, approval |
llm_call |
openai.chat.completions.create(), anthropic.messages.create() |
— |
publish |
s3.send(PutObjectCommand), client.publish() |
approval |
dynamic_code |
eval(), new Function(), vm.runInNewContext() |
confirmation |
file_delete |
fs.rm(), fs.unlink(), fs-extra.remove() |
confirmation |
destructive |
execSync(), spawnSync(), execa() |
confirmation |
What counts as a guard: input validation (Zod, Yup, class-validator), rate limiting (NestJS @Throttle, custom decorators), auth checks (NestJS guards, middleware), confirmation steps, idempotency keys, retry bounds. Full catalog in src/scanner/patterns.ts.
# Scan from your project root (default: current directory)
diplomat-agent-ts scan .
# Or a specific subdirectory
diplomat-agent-ts scan ./src
diplomat-agent-ts scan ./packages
# Generate the toolcalls.yaml SBOM (commit this)
diplomat-agent-ts scan . --output-registry toolcalls.yaml
# Fail CI when new unguarded tool calls appear
diplomat-agent-ts scan . --fail-on-unchecked
# JSON output for IDE agents, automation, custom dashboards
diplomat-agent-ts scan . --format jsonThe scanner emits:
- A coloured ANSI report to stdout (default)
toolcalls.yaml— a diff-stable registry of every detected tool call (with--output-registry)- JSON —
snake_casefield names, interoperable with the Python scanner (--format json)
# .github/workflows/diplomat.yml
- name: Diplomat governance scan
run: npx -y @diplomat-ai/diplomat-agent-ts scan . --fail-on-uncheckedExit code 1 if any tool call has no_checks status. Exit 0 otherwise — even if partial_checks exist (they're warnings, not blockers).
# .pre-commit-config.yaml
repos:
- repo: local
hooks:
- id: diplomat-agent-ts
name: diplomat governance scan
entry: npx -y @diplomat-ai/diplomat-agent-ts scan . --fail-on-unchecked
language: system
pass_filenames: falseThe scanner runs locally in under 10 seconds on typical agent codebases. Ask Claude Code, Copilot, or Cursor to run it after generating tool-calling code:
"Run
diplomat-agent-ts scan .and fix any unguarded tool calls."
Note: AI agents (Claude Code, Copilot, Cursor) may summarize scan output inaccurately when the result is long. Always read the raw stdout — or pipe to a file with
--output report.txtand read that.
When a function is intentionally unguarded or protected outside the static-analysis scope, mark it inline:
// checked:ok — protected by middleware/approval.ts
export async function chargeCustomer(amount: number, customerId: string) {
return stripe.charges.create({ amount, currency: "usd", customer: customerId });
}diplomat:ok and canary:ok are accepted as aliases. The next scan moves the call to confirmed status with an empty missing_hints list. The annotation appears in the YAML registry so reviewers can audit why something was confirmed.
Like package-lock.json, but for what your agent can do, not what it depends on:
spec_version: "1.0"
language: typescript
summary:
total: 12
no_checks: 8
partial_checks: 3
confirmed: 1
tool_calls:
- function: chargeCustomer
file: src/payments.ts
line: 42
actions:
- "return stripe.charges.create({ amount, currency, customer })"
checks: []
missing:
- no bounds on amount
- no rate limit
- no idempotency key
owasp: [ASI-01, ASI-02, ASI-03, ASI-06]Commit it. Diff it in PRs. When your agent gains a new capability, the change shows up in review — before it ships.
Spec → docs/toolcalls-yaml-spec.md
Each finding is tagged with one or more relevant codes from the OWASP Agentic Security Initiative Top 10. The v0.1.0 catalog covers the codes most directly tied to static side-effect detection (ASI-01, ASI-02, ASI-03, ASI-04, ASI-05, ASI-06, ASI-10). Codes that require runtime context (ASI-07 supply chain, ASI-08 misalignment, ASI-09 deception) are out of scope for static analysis — they are covered by diplomat-gate and diplomat.run at runtime.
| Code | Risk | When it fires |
|---|---|---|
ASI-01 |
Excessive Agency | Side effect with no auth check |
ASI-02 |
Tool Misuse | Any side effect (baseline tag) |
ASI-03 |
Privilege Compromise | Payments, deletes, destructive ops with no confirmation |
ASI-04 |
Resource Overload | Agent invocations without bounds |
ASI-05 |
Cascading Hallucination | LLM call chained to side effect |
ASI-06 |
Identity Spoofing | Missing rate limit or retry bound |
ASI-10 |
Overreliance | Nested agent invocations |
Full mapping in src/analyzer/owasp.ts.
Three pure stages, no shared state. See CONTRIBUTING.md for full guidelines.
Real codebases, real numbers.
Methodology. File counts are the number of .ts / .tsx files actually scanned after the scanner's built-in exclusions (node_modules/, dist/, build/, *.test.ts, *.spec.ts, *.d.ts). They can differ from a raw git ls-files count by a few percent. Runs are pinned to the commits below. Findings counts (tool_calls, no_checks, partial) reproduce exactly at those commits; raw file totals on main will drift over time.
| Codebase (scope) | Type | TS files scanned | Tool calls | no_checks |
partial |
Pinned commit |
|---|---|---|---|---|---|---|
OpenClaw (src/) |
Application | 7,874 | 419 | 332 (79%) | 87 | 49d9996d |
Mastra (packages/) |
Framework | 2,777 | 185 | 162 (88%) | 23 | 38b87964 |
OpenAI Agents JS (packages/) |
Framework | 426 | 33 | 31 (94%) | 2 | 629d35af |
OpenAI Agents JS (examples/) |
Examples | 302 | 32 | 28 (88%) | 4 | 629d35af |
Run the benchmarks yourself:
# Application — OpenClaw (pinned commit for reproducibility)
git clone https://github.com/openclaw/openclaw /tmp/openclaw
cd /tmp/openclaw && git checkout 49d9996d && cd -
npx diplomat-agent-ts scan /tmp/openclaw/src
# Framework — Mastra
git clone --depth 1 https://github.com/mastra-ai/mastra /tmp/mastra
npx diplomat-agent-ts scan /tmp/mastra/packages
# Framework + Examples — OpenAI Agents JS
git clone --depth 1 https://github.com/openai/openai-agents-js /tmp/openai-agents
npx diplomat-agent-ts scan /tmp/openai-agents/packages
npx diplomat-agent-ts scan /tmp/openai-agents/examples| Format | Flag | Use case |
|---|---|---|
| Terminal (default) | — | Human review |
| JSON | --format json |
IDE agents, dashboards, automation |
| YAML registry | --format registry or --output-registry FILE |
toolcalls.yaml SBOM, PR diffs |
- Static analysis only — no runtime detection. If a guard is added by middleware or a gateway outside the file, annotate with
// checked:ok — protected by [where]. - Intra-procedural — guard detection looks at the same function or its immediate decorators. Cross-file guard chains require an annotation.
- TypeScript files only —
.tsand.tsxfiles are scanned. Plain.jsfiles are skipped silently. For Python agents, use diplomat-agent. The scanner emits a warning if no.tsfiles are found in the target directory. - ORM patterns require the import — Mongoose, Sequelize, and TypeORM use generic method names (
.save(),.create()), so the patterns are scoped to files that import the ORM. Re-exported models may be missed. - Abstraction layers — if a repo wraps its ORM or HTTP client behind a custom module (e.g.
db.tsre-exporting Prisma without a directimport 'prisma'), call sites in consumers won't carry theimportContainsscope and may be missed. Use// checked:okat the wrapper boundary. - Large repos without tsconfig — scanning 5,000+ files without a
tsconfig.jsoncan take 30–60 s on slower machines (9 s on M-series for 7,874 files). Point at a subdirectory (scan ./src) to reduce scope.
Full limitations and pattern refinement history → docs/limitations.md
- AST scanner with 40+ patterns across 12 categories
-
toolcalls.yamlbehavioral SBOM with diff-stable output - OWASP Agentic Top 10 mapping
- CI integration (
--fail-on-unchecked) -
// checked:okannotations (withdiplomat:ok/canary:okaliases) - Validated against OpenClaw (7,874 files, ~9 s on M-series / ~30 s on x86, pinned commit
49d9996d) - Inter-procedural decorator resolution (v0.2)
- SARIF 2.1.0 output (v0.2)
-
--diff-onlyfor changed files (v0.2) - MCP server scanning (v0.3)
- VS Code extension with inline diagnostics
- Node.js ≥ 20
- 2 runtime dependencies:
ts-morph(TypeScript compiler wrapper),yaml
- diplomat-agent — the original Python scanner
- diplomat-gate — runtime enforcement (CONTINUE / REVIEW / STOP in < 1ms)
- diplomat.run — hosted control plane with hash-chained audit trail
- Questions and ideas → GitHub Discussions
- Bug or false positive → open an issue
- New pattern request → pattern request template
- Security vulnerability → see SECURITY.md
PRs welcome. The architecture above tells you exactly where things live. Read CONTRIBUTING.md first — it explains the "patterns are data, not logic" rule that keeps the matcher simple.
Apache 2.0 — Copyright 2026 Diplomat Services SAS. See LICENSE.