io.github.yaver-io/yaver

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.

• 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

  warn25% of grade

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

  install hook "postinstall" present and not a recognized benign build command; install hook "preuninstall" present and not a recognized benign build command

• 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. src/agent-runtime.js) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  warn15% of grade

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

  has both shell/exec and network egress — capable of download-and-run, though no such path was observed (src/agent-runtime.js: imports child_process and calls exec/spawn; src/hermesc-runtime.js: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (src/agent-runtime.js: imports child_process and calls exec/spawn; src/agent-runtime.js: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: 10 files (src/agent-runtime.js, src/bundler.js, src/commands/deploy.js, +7 more) discloses broad/destructive filesystem access: 7 files (src/agent-runtime.js, src/bundler.js, src/commands/desktop.js, +4 more) 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 1.99.441 (patch bump): new capability primitive(s) in source: child_process, fs-write, http-client, net; new hardcoded outbound host/BCC destination(s): api.github.com, github.com, registry.npmjs.org, unpkg.com, yaver.io.

• Transport config

  fail10% of grade

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

  source performs runtime self-update / download-and-execute (bypasses version_behavior); manifest/source references beacon behavior — disclosure