yana-ai
Audits your AI coding agent setup before it can damage your repo. 55 hooks · 1989 skills · 101 agents · Claude Code + Codex compatible.
This report shows the evidence for yana-ai@0.43.1. 1 of 2 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms unconsented npm postinstall mutation of a broad Claude/AI-agent control surface, which meets the firewall block policy even without observed exfiltration. The behavior is package-aligned safety tooling, but it is activated by lifecycle install rather than an explicit user setup command. Product guard normalized a concrete AI-agent control hijack publish_block to the blockable dangerous-capability shape.
Decision evidence
public snapshot- package.json defines postinstall: node scripts/npm-install.js --auto
- scripts/npm-install.js uses INIT_CWD/process.cwd as TARGET project root
- postinstall copies core/hooks, commands, agents, rules, scripts, gates into TARGET .claude/*
- postinstall also writes .claude-plugin/plugin.json and marketplace.json
- copied .claude-plugin/hooks/hooks.json wires Claude hooks to package shell commands
- No credential harvesting or external exfiltration found in inspected install script
- core/hooks/telemetry-sender.sh writes local .claude/state/telemetry.jsonl only
- scripts/yana-rt-wrapper.js only execFileSyncs explicit/system/package runtime candidates
- No large hidden binary payloads found by size scan
Source & flagged code
25 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
core/hooks/gitnexus-hook.jsView on unpkg · L15Findings
Affected versions and remediation
This report applies to yana-ai@0.43.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing yana-ai@0.43.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.