@testsmith/api-spector-agent@0.5.8
API Spector private runner: monitor internal/local APIs the cloud cannot reach, with no inbound connections.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInstall metadata has no lifecycle hook, and runtime network use is gated on the operator's APP_URL and token. Script execution and result upload stay inside that configured monitoring flow.
Decision evidence
public snapshot- package.json only declares a CLI bin and main entry at dist/index.cjs and has no install lifecycle scripts or dependencies.
- The process exits unless the operator supplies APP_URL and AGENT_TOKEN or RUNTIME_TOKEN, then polls only that configured host.
- Monitor results are posted back to the same APP_URL with the operator token; no other recipient is hardcoded.
- Monitor payloads can include pre-request and post-request scripts that the bundled engine runs in a vm sandbox after the operator starts the CLI.
- A bundled Electron helper can spawn an installer, but the agent path does not call it and the local secret store starts empty.
Source & flagged code
6 flaggedSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.cjsView on unpkg · L247A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @testsmith/api-spector-agent@0.5.8.
See all versions of @testsmith/api-spector-agent for other recorded verdicts.
- Review the evidence and your use of @testsmith/api-spector-agent@0.5.8 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.