registry / @playlist-tech/enterprise-skills / 1.7.1-enterprise.2
@playlist-tech/enterprise-skills@1.7.1-enterprise.2
An enterprise-customizable fork of Vercel Labs' skills CLI for internal skill registries.
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook that mutates agent configuration, and the flagged agent path is a skill installation destination. The inspected setup behavior is command-driven and conditional, so the scanner signals do not establish an attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
The user invokes a CLI command such as setup or a skill installation command.
Impact
These inspected behaviors configure skills and hooks for the CLI’s stated function; no concrete malicious effect was established.
Mechanism
The CLI can place skills in configured agent skill directories; setup writes hooks when an agent configuration exists and a stop command is provided.
AI rationale
The manifest has no install lifecycle hook that mutates agent configuration, and the flagged agent path is a skill installation destination. The inspected setup behavior is command-driven and conditional, so the scanner signals do not establish an attack surface.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json’s prepare hook runs Husky; it has no preinstall, install, or postinstall hook.
- dist/cli.mjs includes .claude/skills among project skill destinations, consistent with the package’s skills CLI function.
- dist/cli.mjs routes setup through an explicit CLI command; it adds hooks only when configured agent paths exist and a stop command is supplied.
- The simple-git helper spawns a command with arguments, consistent with a Git helper; no malicious behavior was identified in the inspected excerpt.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
WildcardDependency
Source & flagged code
3 flaggeddist/_chunks/libs/simple-git.mjsView file
4import { Buffer as Buffer$1 } from "node:buffer";
L5: import { spawn } from "child_process";
L6: import { normalize } from "node:path";
High
Child Process
Package source references child process execution.
dist/_chunks/libs/simple-git.mjsView on unpkg · L4dist/cli.mjsView file
•Manifest-trigger-reachable source links an external AI-agent control path to a behavior-bearing write operation.
;
}
function isvalidrelativepath(path) {
return path.startswith("./");
}
async function getpluginskillpaths(basepath) {
const searchdirs = [];
const addpluginskillpaths = (pluginbase, skills) => {
if (!iscontainedin(pluginbase, basepath)) return;
if (skills && skills.length > 0) for (const skillpath of skills) {
if (!isvalidrelativepath(skillpath)) continue;
const skilldir = dirname(join(pluginbase, skillpath));
if (iscontainedin(skilldir, basepath)) searchdirs.push(skilldir);
}
searchdirs.push(join(pluginbase, "skills"));
};
try {
const content = await readfile(join(basepath, ".claude-plugin/marketplace.json"), "utf-8");
const manifest = json.parse(con
High
Findings
4 High3 Medium5 Low
HighChild Processdist/_chunks/libs/simple-git.mjs
HighShell
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/cli.mjs
HighCross File Remote Execution Contextdist/cli.mjs
MediumNetwork
MediumEnvironment Vars
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @playlist-tech/enterprise-skills@1.7.1-enterprise.2.
See all versions of @playlist-tech/enterprise-skills for other recorded verdicts.
- Review the evidence and your use of @playlist-tech/enterprise-skills@1.7.1-enterprise.2 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.