@wayai/cli@0.3.242
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no install hook, hidden payload execution, or automatic credential redirection. The scanner's decoding and runtime install matches resolve to JWT parsing and a user-invoked self-update; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json declares the CLI entry point and has no install lifecycle hook.
- Browser login sends an authorization code to the configured AuthKit endpoint; the default is the package's AuthKit host.
- Token login prompts for a WayAI token and checks its format before validating it against the selected API URL.
- The API URL defaults to WayAI's service; an alternate URL must be supplied with --api-url.
- The updater checks the published CLI version and installs an update only when the user invokes that command.
- The Hono, Koa, Connect, Fastify, and GraphQL files define framework instrumentation; Hono’s constants file exports its attribute names and types.
- The Knex, Tedious, generic pool, DataLoader, AMQP, Kafka, and LRU memoizer files register instrumentation for their corresponding libraries.
- The Vercel AI, OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph files register instrumentation for their corresponding SDK modules; Vercel AI also exports an integration name.
- The scanner's dynamic decoding match is JWT header parsing, and the package entry point is an explicit CLI rather than an install hook.
Source & flagged code
8 flaggedFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.242.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.242 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.