agentiqa@1.1.98
AI-powered testing for web and mobile apps
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI sends runtime telemetry by default and exposes opt-out controls, but the reviewed source does not disclose the collection to users. The event fields shown are limited to command and runtime metadata, so this is suspicious telemetry rather than data exfiltration.
Decision evidence
public snapshot- The CLI sends `cli_installed` and `cli_invoked` telemetry by default, including command, version, Node version, OS, and CI status.
- Telemetry is posted to `${jt()}/api/t` by default and can be redirected with `AGENTIQA_ANALYTICS_ENDPOINT`; it can be disabled with `DO_NOT_TRACK=1`, `AGENTIQA_TELEMETRY=0`, or the config setting.
- The preinstall hook only checks the Node version and exits on versions below 18.
- The manifest identifies `dist/cli.js` as the executable entry point.
- The telemetry code shown collects package/runtime fields and a generated or persisted distinct ID, not credentials or command output.
- The preinstall hook performs no network requests or project-data collection.
Source & flagged code
13 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to agentiqa@1.1.98.
See all versions of agentiqa for other recorded verdicts.
- Review the evidence and your use of agentiqa@1.1.98 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.