agentiqa@1.1.99
AI-powered testing for web and mobile apps
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI sends default runtime usage telemetry with a persistent ID, but the inspected event fields contain only basic command and runtime metadata, and the code provides opt-outs. No install-time data collection or credential theft was identified, so this warrants a warning rather than a block.
Decision evidence
public snapshot- Normal CLI startup sends a cli_invoked event containing the command, CLI version, Node version, OS, and CI status.
- The first CLI run also sends a cli_installed event and stores an installation marker.
- Telemetry events include a persistent distinct ID and are POSTed to the analytics endpoint, which defaults to Agentiqa's service.
- Telemetry can be disabled with DO_NOT_TRACK=1, AGENTIQA_TELEMETRY=0, or telemetry:false in the CLI config.
- The preinstall hook only checks the Node version and exits on unsupported versions.
- The CLI describes its bring-your-own-key provider feature and checks account entitlement before forwarding provider keys to the embedded engine.
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.99.
See all versions of agentiqa for other recorded verdicts.
- Review the evidence and your use of agentiqa@1.1.99 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.