2 checks that ran failed — credential hygiene and transport config — so this release can’t be trusted as-is.
- Publisher
- io.github.spfunctions
- Install
- npm:@spfunctions/cli, npm:@spfunctions/cli
- Versions
- 2
- Inspected
- 5 of 6 checks · 90%
- Scored
- 2026-07-20 · 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.
Injection surface
warn25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
tool "get_context" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "list_theses" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "inject_signal" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "trigger_evaluation" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "create_thesis" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "create_strategy" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "list_strategies" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "update_strategy" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_forecast" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_settlements" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_balance" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_orders" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_fills" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "what_if" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "augment_tree" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "create_intent" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "list_intents" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "cancel_intent" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "search_x" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "x_volume" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "x_news" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "x_account" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "configure_heartbeat" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "update_thesis" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "add_position" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "update_position" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "close_position" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_evaluation_history" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "update_nodes" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "get_heartbeat_status" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "monitor_the_situation" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "create_skill" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "list_skills" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "run_skill" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "publish_skill" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "fork_skill" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes. tool "fork_thesis" param "apiKey" description: off-vendor URL in a description (simplefunctions.dev); capability text should not name where data goes.
Supply chain
warn25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
package name "@spfunctions/cli" is edit-distance 2 from popular package "chai" (typosquat candidate); dependency "@mariozechner/pi-ai" is edit-distance 2 from popular package "chai" (typosquat candidate)
Credential hygiene
fail15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
tool "get_context" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_theses" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "inject_signal" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "trigger_evaluation" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "create_thesis" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "create_strategy" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_strategies" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "update_strategy" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_forecast" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_settlements" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_balance" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_orders" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_fills" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "what_if" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "augment_tree" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_edges" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "create_intent" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_intents" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cancel_intent" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "search_x" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "x_volume" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "x_news" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "x_account" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "configure_heartbeat" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "update_thesis" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "add_position" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "update_position" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "close_position" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_evaluation_history" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "update_nodes" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_heartbeat_status" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "monitor_the_situation" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "create_skill" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_skills" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "run_skill" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "publish_skill" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "fork_skill" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "fork_thesis" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "read_forum" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "post_to_forum" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "subscribe_forum" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_skills" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_feed" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_changes_delta" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_forum_channels" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_positions" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_positions_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_ledger_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_fills_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_attribution_daily" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_attribution_grouped" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_risk_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portfolio_activity_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_thesis_context" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "tts" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "stt" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_heartbeat_config" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential).
Permission scope
pass15% of gradeDeclared 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
unscannable10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
no prior version to diff (first sight of io.github.spfunctions/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.
Transport config
fail10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)
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.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v1.1.0 · current | 2026-04-02 | D | 50 | 5/6 · 90% | — |