@sentropic/h2a-runtime@0.97.2
h2a heavy runtime (sessions / k8s / tunnel, node-pty + aws-sdk). Lazily imported by @sentropic/h2a; installed separately.
AI Security Review
scanned 26d ago · by lpm-firewall-aiSource inspection supports a clean verdict: the manifest has no install lifecycle hook, and the inspected agent configuration behavior is tied to runtime plugin setup. Scanner hints identify areas for review but do not establish a malicious chain.
Decision evidence
public snapshot- package.json exposes the runtime entrypoints and declares no install lifecycle hook; flagged setup code is reached through explicit runtime commands.
- The plugin code registers MCP servers in agent configuration when its plugin-add flow is invoked; this is an agent capability, but the inspected source does not establish an unconsented install-time mutation.
- Other flagged files handle MCP config path selection, explicit session hooks, local token-expiry advisories, session migration and discovery, PTY loading, auth-file selection, and terminal layout dispatch.
- No concrete malicious behavior was established in the inspected source; the agent configuration writes are part of the plugin-add flow rather than an npm lifecycle hook.
- The package manifest contains no preinstall, install, or postinstall script.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
dist/central-mcp.jsView on unpkg · L21Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/pty.jsView on unpkg · L76Findings
Affected versions and remediation
This report applies to @sentropic/h2a-runtime@0.97.2.
See all versions of @sentropic/h2a-runtime for other recorded verdicts.
- Review the evidence and your use of @sentropic/h2a-runtime@0.97.2 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.