evals@2.8.1
Arize AX onboarding — instrument your app with tracing via your coding agent
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe CLI automatically installs a package-owned agent extension globally as part of the user-selected launch flow, with confirmation disabled. This warrants a warning about persistent agent capability; the postinstall hook itself only prints a message.
Static reason
One or more suspicious static signals were detected.
Trigger
The user selects an installed coding agent to launch through the CLI.
Impact
The skills can remain installed in the agent’s global configuration after the session ends.
Mechanism
The CLI invokes npx to add all skills from Arize-ai/arize-skills globally for the selected agent, with confirmation disabled.
AI rationale
The CLI automatically installs a package-owned agent extension globally as part of the user-selected launch flow, with confirmation disabled. This warrants a warning about persistent agent capability; the postinstall hook itself only prints a message.
Evidence
cli.js
Network endpoints1
Arize-ai/arize-skills
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After the user selects an agent to launch, the CLI runs an Arize skills installation before starting that agent.
- The installer uses npx to add all skills globally for the selected agent, with confirmation disabled; this can persist beyond the session.
- The package specifies Arize-ai/arize-skills as the source of those skills.
Evidence against
- The postinstall hook only prints an installation message; the global skills setup is in the CLI flow, not the install hook.
- The skills setup is tied to the selected agent and the package describes it as Arize onboarding.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node -e "console.log('Arize evals installed — run: npx evals')"
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node -e "console.log('Arize evals installed — run: npx evals')"
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin.jsView file
15//
L16: // MIN_MAJOR tracks ink's own `engines.node`, and package.json's `engines` field
L17: // must say the same thing; test/cli.test.js asserts they agree.
...
L23: if (!Number.isInteger(major) || major < MIN_MAJOR) {
L24: const shell = process.platform === 'win32'
L25: ? 'irm https://cdn.jsdelivr.net/npm/evals/start.ps1 | iex'
L26: : 'bash <(curl -fsSL https://cdn.jsdelivr.net/npm/evals/start.sh)';
High
Sandbox Evasion Gated Capability
Findings
3 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitybin.js
HighShips High Entropy Blobvendor/python_dotenv-1.2.1-py3-none-any.whl
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helperstart.ps1
MediumShips Compressed Blobvendor/python_dotenv-1.2.1-py3-none-any.whl
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNested Archive Needs Inspectionvendor/python_dotenv-1.2.1-py3-none-any.whl
Affected versions and remediation
This report applies to evals@2.8.1.
See all versions of evals for other recorded verdicts.
- Review the evidence and your use of evals@2.8.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.