Is Sign CLI safe and trustworthy?

tashan scores Sign CLI on public evidence — tashan score 46.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, it runs a script at install time, its declared dependencies reach: database. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Sign CLI?

In Claude Code: run `claude mcp add sign-cli -- npx -y @drbaher/sign-cli`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Sign CLI

npm

Agent-first e-signature MCP server with offline PAdES signing and hash-chained audit.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Install (Claude Code):

claude mcp add sign-cli -- npx -y @drbaher/sign-cli

deep

“Full multi-signer command sequences; the signing gesture stays gated behind a human.”

This grade is wrong ›

tashan score: 46.0
Instruction depth: 84.0 (deep — documents every tool, with worked examples, setup and a stated limitation)
Adoption: 105/wk
Upkeep: 57.0
Freshness: 80.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.9.0 — this package, not its dependency tree

Runs a script at install timecodenode scripts/trim-pdfjs-dist.mjs || exit 0

Connects to databasesfrom declared dependencies

Signed build provenancepublished from public CI with an attestation

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Sign CLI scores 46 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-drbaher-sign-cli.svg)](https://tashan.sh/capability/pkg-drbaher-sign-cli.html)

npm ↗ · source ↗ · pkg:@drbaher/sign-cli

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?