@testsmith/api-spector-agent@0.9.1
API Spector private runner: monitor internal/local APIs the cloud cannot reach, with no inbound connections.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package’s network and credential use matches its documented private-runner purpose: it uses a user-configured API Spector Cloud URL and token to run monitors and return results. The scanner’s foreign-host leads do not establish credential redirection or unrelated exfiltration in the runner code.
Decision evidence
public snapshot- The manifest exposes the bundled runner as both the CLI and CommonJS entry point and has no lifecycle scripts.
- The README describes a private API monitor that polls API Spector Cloud, runs due checks, and posts results.
- The documented APP_URL is the user’s API Spector Cloud URL; AGENT_TOKEN is described as scoped to the agent ability.
- The runner reads APP_URL and its token from environment variables, polls the due-monitor endpoint, runs returned monitors, and posts their results to that configured URL.
- The CLI exits unless APP_URL and a runner token are configured, then starts polling.
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.9.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.9.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.