happyskills@1.16.1
Package manager for AI agent skills
AI Security Review
scanned 4mo ago · by lpm-firewall-aiStatic inspection found no lifecycle execution, hidden payload, credential harvesting, or unsolicited AI-agent control-surface mutation. The suspicious primitives are expected for a user-invoked skill package manager and are constrained to documented CLI workflows.
Decision evidence
public snapshot- package.json has no install/preinstall/postinstall lifecycle scripts; bin is explicit CLI at bin/happyskills.js.
- src/index.js only dispatches whitelisted commands from constants.js, then requires ./commands/<resolved>.
- src/commands/self-update.js runs npm install -g happyskills@latest only when user invokes self-update.
- src/api/client.js sends requests to https://api.happyskills.ai or env override for registry operations.
- src/engine/installer.js downloads skills, writes .agents/skills and skills-lock.json, and links configured agent skill dirs as package-aligned install behavior.
- src/utils/scrub_secrets.test.js contains synthetic token patterns used to test redaction, not real embedded secrets.
Source & flagged code
6 flaggedPackage contains a critical-looking secret pattern.
src/utils/scrub_secrets.test.jsView on unpkg · L16AWS access key ID in src/utils/scrub_secrets.test.js
src/utils/scrub_secrets.test.jsView on unpkg · L16Package source references child process execution.
Findings
Affected versions and remediation
This report applies to happyskills@1.16.1.
See all versions of happyskills for other recorded verdicts.
- Review the evidence and your use of happyskills@1.16.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.