agentiqa@1.1.80
AI-powered testing for web and mobile apps
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe credential source, configurable destination, and request sink are connected in the CLI, so conditional token exposure remains a concrete risk. The destination requires an environment override, and the install hook only enforces the Node.js version; the evidence does not support blocking the package.
Decision evidence
public snapshot- The CLI reads a saved token from its credentials file and uses it as a bearer credential for an analytics request.
- The analytics destination can be set through an environment variable, and telemetry sends unless disabled by configuration or certain CI conditions.
- The install hook only checks the Node.js version and exits on unsupported versions.
- The manifest’s install hook runs a Node.js version check; it does not install another package or change consumer configuration.
- The inspected credential forwarding is in telemetry, and the destination override must be set in the environment.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsFindings
Affected versions and remediation
This report applies to agentiqa@1.1.80.
See all versions of agentiqa for other recorded verdicts.
- Review the evidence and your use of agentiqa@1.1.80 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.