agentic-awesome-skills@17.7.0
AAS Core: complete local skill discovery, agent-owned selection, stack validation, and planning, backed by 2,141+ agentic skills.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo malicious install hook, covert exfiltration, remote payload execution, or reviewer manipulation was found. The remaining risk is the explicit installer changing AI-agent skill directories.
Decision evidence
public snapshot- The package exposes a user-invoked installer executable and targets Codex's skills directory when --codex is supplied.
- That installer clones a repository, then copies, removes, and records managed skill entries in the selected AI-agent skills directory.
- The manifest has no npm preinstall, install, or postinstall hook, so this behavior is not activated during package installation.
- The Apify example sends its explicitly supplied APIFY_TOKEN only to api.apify.com when the example script is run.
- The Hugging Face example uses HF_TOKEN only as authentication for huggingface.co.
- The Fedora shell file is an isolated, non-destructive test that replaces HOME with a temporary directory.
- The PDF is a normal ReportLab-generated document; no executable payload was established.
Source & flagged code
10 flagged · loading sourcePackage contains a high-severity secret pattern.
skills/developer-signup-flow/SKILL.mdView on unpkg · L165Stripe test secret key in skills/developer-signup-flow/SKILL.md
skills/developer-signup-flow/SKILL.mdView on unpkg · L165Package source references dynamic require/import behavior.
tools/bin/aas.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to agentic-awesome-skills@17.7.0.
See all versions of agentic-awesome-skills for other recorded verdicts.
- Review the evidence and your use of agentic-awesome-skills@17.7.0 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.