MCP server · trust report

sh.tashan/tashan

2 checks that ran failed — permission scope and version behavior — so this release can’t be trusted as-is.

Publisher
sh.tashan
Repository
github.com/FlyingWHR/tashan
Install
npm:tashan-cli, npm:tashan-cli
Versions
2
Inspected
5 of 6 checks · 75%
Scored
2026-09-02 · rubric 1.0.0

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

6 checks2 clean3 flagged1 not inspected
  • Injection surface

    unscannable25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

  • Supply chain

    pass25% of grade

    Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

    repository linkage verified

  • Credential hygiene

    pass15% of grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    Reads secrets from the environment (e.g. mcp.mjs) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    fail15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    HIGH: tashan.mjs reads a credential path, executes commands, and makes network calls in the same file — the combination that makes exfiltration possible. references credential paths: tashan.mjs: references a credential path (/.cursor/) has both shell/exec and network egress — capable of download-and-run, though no such path was observed (tashan.mjs: imports child_process and calls exec/spawn; tashan.mjs: outbound HTTP/socket call). discloses shell/exec capability: tashan.mjs: imports child_process and calls exec/spawn Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • Version behavior

    fail10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 0.1.3 (patch bump): new capability primitive(s) in source: child_process, http-client; new hardcoded outbound host/BCC destination(s): api.polar.sh, github.com, polar.sh, registry.npmjs.org, tashan.sh, www.npmjs.com.

  • Transport config

    warn10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    manifest/source references beacon behavior — disclosure

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v0.1.4 · current2026-08-09 C705/6 · 75%B→C in v0.1.4
v0.1.32026-08-07 B1003/6 · 55%