@testsmith/api-spector-agent@0.8.5
API Spector private runner: monitor internal/local APIs the cloud cannot reach, with no inbound connections.
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection shows a runner configured through operator-provided environment values, with polling and result reporting directed to that configured application. The scanner's execution and network signals are consistent with the bundled API-monitoring functionality; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest points both the CLI and main entrypoint to dist/index.cjs and declares no lifecycle hook.
- The runner reads APP_URL and its runner token from the operator's environment.
- Startup exits unless APP_URL and a runner token are configured.
- The runner polls for monitoring tasks and posts results to endpoints under the configured APP_URL.
- Reported results include sent and received headers and bodies, consistent with the private monitoring runner's stated function.
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.5.
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.5 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.