io.github.industrial-aiops/iaiops

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

  warn15% of grade

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

  tests/test_credential_redaction_contract.py: assigns a literal to token (SUPE…EN (len 18)) — non-provider secret literal; prefer environment intake. tests/test_egress_live.py: assigns a literal to token (SUPE…ET (len 12)) — non-provider secret literal; prefer environment intake. Reads secrets from the environment (e.g. iaiops/cli/secret.py) — the recommended intake shape.

• 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 (iaiops/core/discovery/passive.py: subprocess.* call; demo/oee-line/run_demo.sh: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (iaiops/core/discovery/passive.py: subprocess.* call; iaiops/core/governance/approvals.py: destructive filesystem call (shutil.rmtree/os.remove/etc.)). discloses shell/exec capability: iaiops/core/discovery/passive.py: subprocess.* call discloses shell/exec capability: iaiops/core/verify/determinism.py: subprocess.* call discloses broad/destructive filesystem access: 5 files (iaiops/core/governance/approvals.py, iaiops/core/governance/audit.py, iaiops/core/governance/evidence.py, +2 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 0.26.0 (minor bump): new capability primitive(s) in source: fs-write, http-client, net, subprocess; new hardcoded outbound host/BCC destination(s): 127.0.0.1, 192.168.0.10, acme.example, aiops.test, attacker.example.com, bms, bms-host, bms.acme.example, github.com, gw, gw-host, gw.acme.example, h, host, opcfoundation.org, schemas.mtconnect.org, siem.example.com, tok, unused, www.w3.org, x.example.com.

• Transport config

  warn10% of grade

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

  sends telemetry to third-party SDK (amplitude) — disclosure, verify opt-in; manifest/source references analytics behavior — disclosure