io.github.Developyn/laver-mcp

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

  warn25% of grade

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

  tool "update_ticket" description: imperative telling the model it must read/send/attach something. tool "create_wiki_page" description: off-vendor URL in a description (…); capability text should not name where data goes.

• Supply chain

  warn25% of grade

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

  package name "@laver/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate)

• Credential hygiene

  pass15% of grade

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

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• Permission scope

  pass15% of grade

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

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• 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.4.0 (minor bump): new tool "list_workspaces" touches a sensitive surface (email/exec/net/fs); new tool "list_boards" touches a sensitive surface (email/exec/net/fs); new tool "get_board" touches a sensitive surface (email/exec/net/fs); new tool "list_tickets" touches a sensitive surface (email/exec/net/fs); new tool "search" appeared; new tool "list_workspace_tickets" touches a sensitive surface (email/exec/net/fs); new tool "get_ticket" touches a sensitive surface (email/exec/net/fs); new tool "get_ticket_comments" touches a sensitive surface (email/exec/net/fs); new tool "get_ticket_flow" touches a sensitive surface (email/exec/net/fs); new tool "list_ticket_attachments" touches a sensitive surface (email/exec/net/fs); new tool "get_ticket_attachment" touches a sensitive surface (email/exec/net/fs); new tool "create_ticket" touches a sensitive surface (email/exec/net/fs); new tool "update_ticket" touches a sensitive surface (email/exec/net/fs); new tool "move_ticket" touches a sensitive surface (email/exec/net/fs); new tool "comment_on_ticket" touches a sensitive surface (email/exec/net/fs); new tool "update_comment" touches a sensitive surface (email/exec/net/fs); new tool "delete_comment" touches a sensitive surface (email/exec/net/fs); new tool "mark_comments_read" touches a sensitive surface (email/exec/net/fs); new tool "add_subtask" touches a sensitive surface (email/exec/net/fs); new tool "update_subtask" touches a sensitive surface (email/exec/net/fs); new tool "delete_subtask" touches a sensitive surface (email/exec/net/fs); new tool "upload_ticket_attachment" touches a sensitive surface (email/exec/net/fs); new tool "delete_ticket_attachment" touches a sensitive surface (email/exec/net/fs); new tool "archive_ticket" touches a sensitive surface (email/exec/net/fs); new tool "delete_ticket" touches a sensitive surface (email/exec/net/fs); new tool "link_tickets" touches a sensitive surface (email/exec/net/fs); new tool "unlink_tickets" touches a sensitive surface (email/exec/net/fs); new tool "create_board" appeared; new tool "create_status" touches a sensitive surface (email/exec/net/fs); new tool "update_status" touches a sensitive surface (email/exec/net/fs); new tool "reorder_statuses" touches a sensitive surface (email/exec/net/fs); new tool "delete_status" touches a sensitive surface (email/exec/net/fs); new tool "create_group" appeared; new tool "reorder_groups" touches a sensitive surface (email/exec/net/fs); new tool "delete_group" touches a sensitive surface (email/exec/net/fs); new tool "list_custom_fields" touches a sensitive surface (email/exec/net/fs); new tool "create_custom_field" touches a sensitive surface (email/exec/net/fs); new tool "update_custom_field" touches a sensitive surface (email/exec/net/fs); new tool "delete_custom_field" touches a sensitive surface (email/exec/net/fs); new tool "list_labels" touches a sensitive surface (email/exec/net/fs); new tool "create_label" appeared; new tool "update_label" touches a sensitive surface (email/exec/net/fs); new tool "delete_label" touches a sensitive surface (email/exec/net/fs); new tool "list_automations" touches a sensitive surface (email/exec/net/fs); new tool "create_automation" touches a sensitive surface (email/exec/net/fs); new tool "get_automation" touches a sensitive surface (email/exec/net/fs); new tool "list_automation_runs" touches a sensitive surface (email/exec/net/fs); new tool "update_automation" touches a sensitive surface (email/exec/net/fs); new tool "delete_automation" touches a sensitive surface (email/exec/net/fs); new tool "list_published_links" touches a sensitive surface (email/exec/net/fs); new tool "list_wikis" touches a sensitive surface (email/exec/net/fs); new tool "restore_wiki" touches a sensitive surface (email/exec/net/fs); new tool "search_wiki" appeared; new tool "get_wiki_tree" appeared; new tool "get_wiki_page" touches a sensitive surface (email/exec/net/fs); new tool "get_wiki_page_version" touches a sensitive surface (email/exec/net/fs); new tool "create_wiki_page" whose description contains embedded outbound URL; new tool "append_wiki_page" touches a sensitive surface (email/exec/net/fs); new tool "update_wiki_page" touches a sensitive surface (email/exec/net/fs).

• Transport config

  unscannable10% of grade

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

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.