@sentropic/h2a-runtime@0.97.3
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-aiThe source implements agent configuration changes as part of plugin management, while the manifest has no install lifecycle hook. This is a warning-level agent capability, not evidence of malicious execution or an unconsented npm install-time control-surface change.
Decision evidence
public snapshot- The package exposes the runtime through its import entry and declares no npm lifecycle hook.
- The plugin command writes an MCP server entry into the user's Codex configuration.
- The plugin installer records an install method for later remote plugin synchronization.
- The Pod setup code edits Claude's user configuration to merge MCP settings.
- The observed agent configuration changes are part of explicit plugin setup flows, not npm installation hooks.
- The inspected source does not establish credential exfiltration or an active attack.
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.3.
See all versions of @sentropic/h2a-runtime for other recorded verdicts.
- Review the evidence and your use of @sentropic/h2a-runtime@0.97.3 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.