AI Security Review
scanned 3d ago · by lpm-firewall-aiLPM blocks this version under the AI-agent control-surface policy. The package mutates an AI-agent skill directory during npm postinstall and runs a bundled Python helper. This is an unconsented lifecycle write to an agent control surface outside node_modules.
Decision evidence
public snapshot- package.json defines postinstall: node install.js and bin hyper-animator -> install.js
- install.js copies skills/hyper-animator to ~/.claude/skills/hyper-animator on default postinstall path
- install.js creates/updates ~/.claude/skills/hyper-animator/.env with MiniMax config placeholders
- install.js executes child_process.execSync('python3 .../scripts/sync-catalog.py --workers 4') from the dropped skill directory
- sync-catalog.py writes ~/.claude/skills/hyper-animator/references/source-cache and shells out to hyperframes add
- No credential harvesting found; scripts read MINIMAX_API_KEY only for user-invoked MiniMax API calls
- Network/API behavior is aligned with animation, TTS, music generation, and HyperFrames catalog sync
- No obfuscation, destructive commands, native binaries, dependency confusion, or reviewer prompt injection found
- No npm dependencies declared
Source & flagged code
4 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 unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
install.jsView on unpkg · L12Package ships non-JavaScript build or shell helper files.
skills/hyper-animator/scripts/preview-gen.pyView on unpkg