@playlist-tech/enterprise-skills@1.6.0-enterprise.1
An enterprise-customizable fork of Vercel Labs' skills CLI for internal skill registries.
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe source supports a benign verdict: npm lifecycle behavior is build and Husky setup, while agent hook wiring is part of explicit CLI skill installation and requires caller-supplied configuration. The scanner's process-execution signal comes from a bundled Git helper and does not establish malicious behavior.
Decision evidence
public snapshot- The prepare hook only runs Husky setup, and prepublishOnly runs the build.
- The CLI lists supported agent skill directories, including Claude, Codex, and Continue locations.
- An explicit skill installation can add a prompt hook for each selected agent; the command is supplied through SKILLS_HOOK_START_CMD.
- Hook wiring requires a configured hooks file, prompt event, schema, and a nonempty command template containing a skill-name placeholder.
- The bundled simple-git helper imports child_process spawn as part of a Git library.
- The hook setup is reached after the CLI completes an installation command, not through the package's npm lifecycle hooks.
- Without SKILLS_HOOK_START_CMD, prompt-hook wiring returns without adding a hook.
- No source evidence establishes a hidden payload, credential theft, or unconsented install-time agent configuration change.
Source & flagged code
3 flaggedPackage source references child process execution.
dist/_chunks/libs/simple-git.mjsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @playlist-tech/enterprise-skills@1.6.0-enterprise.1.
See all versions of @playlist-tech/enterprise-skills for other recorded verdicts.
- Review the evidence and your use of @playlist-tech/enterprise-skills@1.6.0-enterprise.1 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.