@wayai/cli@0.3.252
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or hidden-code execution. The scanner’s runtime install signal is an explicit update command, while login uses the package’s configured WayAI and AuthKit endpoints.
Decision evidence
public snapshot- package.json identifies dist/index.js as the CLI entry point and shows no install lifecycle hook.
- The login flow exchanges an authorization code through the configured AuthKit domain using PKCE.
- The CLI selects browser login or token login only when the login command is invoked.
- The default API endpoint is the WayAI service at api.wayai.pro.
- The package install command is reached through the explicit update command dispatch.
- Sentry initialization can be disabled with WAYAI_TELEMETRY_DISABLED=1 and is limited to installed packages unless SENTRY_DSN is explicitly set.
- Hono tracing defines middleware and request-handler attributes and imports OpenTelemetry tracing APIs.
- Koa, Connect, Knex, Tedious, generic-pool, and DataLoader files are framework or client instrumentation modules using OpenTelemetry or Sentry instrumentation helpers.
- The runtime package installation is inside the user-invoked update command and installs this CLI package.
- The inspected login flow uses the package’s configured AuthKit and WayAI service endpoints; no unrelated credential recipient was found.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.252.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.252 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.