@testsmith/api-spector-agent@0.8.1
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 and inspected entrypoint support the private monitoring purpose. Network destinations and credentials are supplied by the caller, and the suspicious VM and process-execution matches do not establish package-directed attack behavior.
Decision evidence
public snapshot- The manifest describes a private runner for monitoring internal and local APIs, and points its CLI and module entry to dist/index.cjs.
- The runner requires caller-provided APP_URL and an AGENT_TOKEN or RUNTIME_TOKEN before polling begins.
- It polls for monitors and posts results to API paths under the configured APP_URL, using the configured token.
- Monitor scripts are run in a VM sandbox with a timeout as part of the runner’s request-testing flow.
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.1.
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.1 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.