@testsmith/api-spector-agent@0.7.4
API Spector private runner: monitor internal/local APIs the cloud cannot reach, with no inbound connections.
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the executable source uses caller-provided configuration to authenticate to the configured monitoring service. Scanner signals such as VM execution correspond to bundled expression-evaluation dependencies; no concrete attack behavior was found in the inspected active entrypoint.
Decision evidence
public snapshot- package.json exposes a CLI and main entrypoint in the bundled file and declares no install lifecycle hook.
- The entrypoint reads the app URL and authentication token from caller-provided environment variables, then uses them for the runtime API.
- Startup requires both a configured app URL and a token; the process polls that app for monitor jobs.
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.7.4.
See all versions of @testsmith/api-spector-agent for other recorded verdicts.
- Review the evidence and your use of @testsmith/api-spector-agent@0.7.4 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.