Security Audit
linkerd-patterns
github.com/sickn33/antigravity-awesome-skillsTrust Assessment
linkerd-patterns received a trust score of 26/100, placing it in the Untrusted category. This skill has significant security findings that require attention before use in production.
SkillShield's automated analysis identified 3 findings: 2 critical, 1 high, 0 medium, and 0 low severity. Key findings include Arbitrary command execution, Remote code execution: curl/wget pipe to shell, Unpinned Remote Script Execution via curl | sh.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 20, 2026 (commit e36d6fd3). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings3
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| CRITICAL | Arbitrary command execution Remote code download piped to interpreter Review all shell execution calls. Ensure commands are static (not built from user input), use absolute paths, and are strictly necessary. Prefer library APIs over shell commands. | Manifest | skills/linkerd-patterns/SKILL.md:66 | |
| CRITICAL | Remote code execution: curl/wget pipe to shell Detected a pattern that downloads and immediately executes remote code. This is a primary malware delivery vector. Never pipe curl/wget output directly to a shell interpreter. | Static | skills/linkerd-patterns/SKILL.md:66 | |
| HIGH | Unpinned Remote Script Execution via curl | sh The skill suggests installing the Linkerd CLI by piping the output of a `curl` command directly to `sh`. This practice, `curl ... | sh`, executes code downloaded from a remote URL without prior inspection or verification (e.g., checksum, specific version pinning). If the remote server (`run.linkerd.io`) were compromised, or if the script content changed unexpectedly, it could lead to arbitrary code execution on the user's system, posing a significant supply chain risk. Avoid piping `curl` output directly to `sh`. Instead, download the script to a temporary file, inspect its contents, and then execute it. Alternatively, use a package manager if available, or verify the script against a known checksum or specific version before execution. | LLM | SKILL.md:79 |
Scan History
Embed Code
[](https://skillshield.io/report/e18dd77600fe495c)
Powered by SkillShield