agent-qa@0.2.4
The self-improving Agentic QA harness with Memory
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe CLI emits runtime analytics during ordinary operations and exposes a configuration opt-out, but the package README does not disclose the telemetry. The inspected event examples do not establish credential or content exfiltration, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Runtime initialization, CLI setup, and MCP server lifecycle.
Impact
Product usage and an analytics identity may be sent to the analytics service. The transport dependency was not available to confirm its full payload or destination.
Mechanism
The CLI uses @vostride/agent-qa-analytics, supports a PostHog transport, resolves an analytics identity, and emits usage events; a configuration privacy flag is the visible opt-out.
AI rationale
The CLI emits runtime analytics during ordinary operations and exposes a configuration opt-out, but the package README does not disclose the telemetry. The inspected event examples do not establish credential or content exfiltration, so this warrants a warning rather than a block.
Evidence
dist/cli-main.js
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI loads its analytics implementation from @vostride/agent-qa-analytics.
- The analytics host branches on PostHog transport and resolves an analytics identity; events include package version and runtime surface.
- Normal CLI operations emit analytics events, including initialization and MCP server lifecycle events.
- The visible privacy control only enables privacy mode when analytics.privacy is true in configuration; README.md does not disclose analytics.
Evidence against
- package.json has no install lifecycle scripts.
- The visible event examples contain usage and lifecycle fields; inspected code did not show credentials or user prompts being sent.
- The analytics transport implementation is in a dependency whose source was unavailable in this snapshot.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
Source & flagged code
5 flaggeddist/cli-main.jsView file
4700import { randomUUID as randomUUID4 } from "crypto";
L4701: import { spawnSync } from "child_process";
L4702: import {
High
Child Process
Package source references child process execution.
dist/cli-main.jsView on unpkg · L470019237// Do not inherit `--input-type=module` or test loaders that would reinterpret eval as ESM.
L19238: execArgv: [],
L19239: name: "agent-qa-writer-lease-heartbeat",
High
33"use strict";
L34: RE_INITIALIZE_URL = "https://vostride.com/docs/agent-qa/migrate/v0-1-to-v0-2";
L35: HARD_CUT_STEPS = [
...
L157: for (const [envKey, configPath] of Object.entries(ENV_MAPPING)) {
L158: const value = process.env[envKey];
L159: if (value !== void 0) {
...
L700: try {
L701: parsed = JSON.parse(bodySeed);
L702: } catch {
...
L1279: summary: bundle.summary,
L1280: body: bundle.body,
L1281: distilledEvidenceRef: {
High
Hidden Inline Dependency Execution
Source silently spawns a Node process to execute an inline dependency payload.
dist/cli-main.jsView on unpkg · L33Findings
4 High4 Medium4 Low
HighChild Processdist/cli-main.js
HighShelldist/cli-main.js
HighHidden Inline Dependency Executiondist/cli-main.js
HighRuntime Package Installdist/cli-main.js
MediumDynamic Requiredist/index.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to agent-qa@0.2.4.
See all versions of agent-qa for other recorded verdicts.
- Review the evidence and your use of agent-qa@0.2.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.