typescript-package-manager
A documentation-reference skill for TypeScript package management that transparently discloses risks, defaults to read-only guidance, and requires explicit user approval for mutating actions — but documents dangerous curl|bash installer patterns that could be executed by an AI agent without adequate safeguards.
Why this conclusion was reached
1/4 dimensions flaggedDeclared resources and inferred behavior are broadly aligned.
3 high-risk artifacts or egress signals were extracted.
There is no explicit malicious chain in the report.
Dependency information is incomplete, so supply-chain confidence stays limited.
What drove the risk score up
SKILL.md prominently documents 'curl -fsSL https://bun.sh/install | bash' which executes remote code; mitigation is buried in prose and easy to skip in agent context
bun-workflow.js.txt and health-check.js.txt use child_process.execSync for shell commands but the declared allowed-tools only mentions Read and Write
Skill explicitly requires user approval and diff review for mutating actions; skill-card.md lists all known risks with mitigations
No evidence of data exfiltration, credential harvesting, obfuscation, or supply-chain attacks
Inert .js.txt naming is a soft guardrail; an AI agent could theoretically instruct a user to rename and run these without reading
Most important evidence
curl|bash remote installer commands documented without strong safeguards
SKILL.md prominently features 'curl -fsSL https://bun.sh/install | bash' and 'curl -fsSL https://get.pnpm.io/install.sh | sh' as recommended installation methods. These commands download and execute arbitrary code from the network at execution time. While the Safety and Trust Model section warns about this, the warning is prose-only and easy to skip in an agent context. No version pinning is enforced for these installers.
SKILL.md:13 Shell execution capability not declared in allowed-tools
The skill declares filesystem:READ but bun-workflow.js.txt:45 and health-check.js.txt:47 use child_process.execSync to run local shell commands (bun --version, node --version). While SKILL.md mentions 'shell out to local tools via child_process.execSync', this is not reflected in the declared capability map.
SKILL.md:309 .js.txt extension is a weak guardrail against script execution
Helper scripts ship with .js.txt extension so they are 'not directly executable'. While this prevents accidental double-click execution, an AI agent could instruct a user to rename bun-workflow.js.txt to bun-workflow.js and run it without reading, bypassing the safety intent. No cryptographic integrity check or hash verification exists.
SKILL.md:12 Declared capability vs actual capability
SKILL.md states 'read-only guidance'; no filesystem:WRITE declared or observed in scripts bun-workflow.js.txt:45 uses execSync('bun --version'); health-check.js.txt:47 uses execSync; SKILL.md line 309 mentions shell out to local tools but declared capabilities do not include shell Documentation references URLs (bun.sh, pnpm.io) but no actual network calls; network access is described in docs for user context only No iteration through os.environ or environment variable access observed Skill does not invoke other skills No clipboard access observed No browser access observed No database access observed Suspicious artifacts and egress
curl -fsSL https://bun.sh/install | bash SKILL.md:13
curl … | bash SKILL.md:309
curl -fsSL https://get.pnpm.io/install.sh | sh scripts/pnpm-workflow.md:51
https://bun.sh/install SKILL.md:13
https://yourwebsite.com assets/package-json-template.md:25
https://docs.npmjs.com/cli/v9/configuring-npm/package-json assets/package-json-template.md:521
https://nodejs.org/api/packages.html assets/package-json-template.md:522
https://www.typescriptlang.org/docs/handbook/module-resolution.html assets/package-json-template.md:523
https://www.typescriptlang.org/docs/handbook/integrating-with-build-tools.html references/integration-with-build-tools.md:13
https://vitejs.dev/guide/ references/integration-with-build-tools.md:614
https://webpack.js.org/concepts/ references/integration-with-build-tools.md:615
https://esbuild.github.io/ references/integration-with-build-tools.md:616
Dependencies and supply chain
There are no structured dependency warnings.
File composition
scripts/health-check.md scripts/npm-workflow.md scripts/yarn-workflow.md scripts/bun-workflow.md scripts/bun-workflow.js.txt SKILL.md scripts/pnpm-workflow.md references/integration-with-build-tools.md assets/package-json-template.md