io.github.Shakargy/devtime

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

  pass25% of grade

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

  Python build script has no build-time network/exec; repository linkage verified

• Credential hygiene

  fail15% of grade

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

  src/devtime/privacy.py: embeds a PRIVATE KEY block. Reads secrets from the environment (e.g. src/devtime/resources/demo-saas/src/auth/login.ts) — the recommended intake shape.

• Permission scope

  fail15% of grade

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

  HIGH: src/devtime/scanner/ignore.py: references a sensitive credential path (id_rsa) — the tool-poisoning exfiltration target. HIGH: shell/exec capability AND destructive filesystem writes together (src/devtime/cli.py: subprocess.* call; src/devtime/cli.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: src/devtime/cli.py: subprocess.* call discloses shell/exec capability: src/devtime/privacy.py: subprocess.* call discloses broad/destructive filesystem access: src/devtime/cli.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) discloses broad/destructive filesystem access: src/devtime/demo.py: destructive filesystem call (shutil.rmtree/os.remove/etc.) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

• Version behavior

  unscannable10% of grade

  Diff 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.Shakargy/[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

  warn10% of grade

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

  manifest/source references Telemetry behavior — disclosure