@wayai/cli@0.3.176
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe harness directories are first-party skill locations used by an explicit authenticated install command and by a local symlink to a skill already on disk. package.json has no install hook, so this is user-invoked product behavior rather than an unconsented agent control-surface write.
Decision evidence
public snapshot- package.json exposes the wayai bin at dist/index.js and only build, dev, typecheck, and test scripts, with no preinstall, install, or postinstall hook.
- HARNESS_SKILL_DIRS lists .claude, .opencode, and .agents as local skill locations. Writing skill files there happens only in the authenticated admin skill-install command, which fetches the skill from the user's configured WayAI API and writes it under existing harness directories.
- healClaudeSkillLink runs only after a user starts a non-help wayai command, and it creates a .claude/skills/wayai symlink only when .agents/skills/wayai/SKILL.md already exists.
- Any ordinary wayai command can create that Claude skill symlink without a separate confirmation prompt.
- Background refresh can fetch the public WayAI skill URL and the authenticated admin skill endpoint, but those paths cache a version string and do not execute the body.
Source & flagged code
7 flaggedManifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @wayai/cli@0.3.176.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.176 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.