@wayai/cli@0.3.250
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection supports ordinary WayAI CLI authentication and opt-out-capable, secret-masking telemetry; the scanner’s suspicious labels were not verified as executable attack behavior. The manifest has no install lifecycle hook.
Decision evidence
public snapshot- The manifest exposes dist/index.js as the wayai CLI entrypoint and has no install lifecycle hook.
- The CLI prompts for a WayAI token, validates it against its configured API, and stores it in the OS keyring.
- The default API endpoint is api.wayai.pro, matching the package’s WayAI CLI purpose.
- Sentry telemetry is disabled by an environment opt-out; token identifiers are hashed and string extras are masked before reporting.
- The Hono constants define middleware and request-handler labels; the Hono, Koa, and Connect excerpts identify Sentry instrumentation and framework patching.
- The Knex, Tedious, generic-pool, and dataloader excerpts identify Sentry instrumentation for database, pool, and cache-related operations.
- The excerpts identify Sentry instrumentation for amqplib, OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph; the Vercel AI integration lists model-call methods it instruments.
- The Firebase file identifies a Sentry Firebase instrumentation class, and the filesystem module catalogs filesystem operations, including path-based calls.
- Static scanner labels suggest a hidden payload loader and credential redirect, but inspected entrypoint excerpts do not establish either behavior.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.250.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.250 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.