evals@2.11.1
Arize AX onboarding — instrument your app with tracing via your coding agent
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s runtime onboarding flow sends event telemetry linked by a stable anonymous ID without an apparent opt-out or CLI disclosure, so this merits a warning. The inspected payload is limited to event names and that ID, and the install hook only prints a message.
Decision evidence
public snapshot- Runtime analytics posts allowlisted onboarding event names to Arize’s analytics endpoint.
- The analytics payload contains the event name and a stable anonymous client ID.
- The CLI sends an analytics event after the user selects an agent and starts the onboarding flow.
- The postinstall script only prints a message; it does not contact the network.
- The analytics code limits events and does not include credentials or project contents in its payload.
- The onboarding prompt describes an anonymous funnel ping before OAuth, and the remaining setup is tied to the onboarding flow.
Source & flagged code
8 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 evals@2.11.1.
See all versions of evals for other recorded verdicts.
- Review the evidence and your use of evals@2.11.1 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.