@testsmith/api-spector-agent@0.7.9
API Spector private runner: monitor internal/local APIs the cloud cannot reach, with no inbound connections.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe package manifest has no install lifecycle hook, and its entrypoint requires an explicitly configured service URL and token. The inspected polling, result reporting, and subprocess use are consistent with the private monitoring runner; the scanner signals alone do not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes dist/index.cjs as the CLI and main entrypoint, with no lifecycle hook listed.
- The runner requires APP_URL and an AGENT_TOKEN or RUNTIME_TOKEN, then polls the configured service and posts monitor results there.
- The flagged child-process call is in bundled synchronous XMLHttpRequest support; inspected source shows it launching a Node subprocess to handle that request.
Source & flagged code
8 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.cjsView on unpkgSource combines command execution, command-output handling, and outbound requests; review data flow before blocking.
Findings
Affected versions and remediation
This report applies to @testsmith/api-spector-agent@0.7.9.
See all versions of @testsmith/api-spector-agent for other recorded verdicts.
- Review the evidence and your use of @testsmith/api-spector-agent@0.7.9 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.