@testsmith/api-spector-agent@0.8.0
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 manifest has no install-time hooks, and the executable’s network activity is tied to a required, operator-configured cloud URL and token. Sending monitor request and response data to that configured service is consistent with the private runner’s function; the scanner’s suspicious signals do not establish a separate attack.
Decision evidence
public snapshot- package.json exposes dist/index.cjs as the package entrypoint and CLI; it declares no lifecycle hooks.
- The agent reads its cloud URL and authentication token from environment variables, then polls that configured service.
- It posts monitor results, including request and response headers and bodies, to the configured cloud service as part of its runner workflow.
- The executable requires the cloud URL and an agent token before starting; no fixed credential recipient or hidden installation trigger was identified.
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.8.0.
See all versions of @testsmith/api-spector-agent for other recorded verdicts.
- Review the evidence and your use of @testsmith/api-spector-agent@0.8.0 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.