扫描报告
5 /100
jest-unittest
Jest-based unit test management skill providing coverage detection, auto-completion to 100%, and test failure diagnosis/fixing for frontend projects
Jest-based unit test management skill with well-documented functionality, appropriate permissions, and no malicious indicators.
可以安装
This skill is safe to use. No security concerns identified.
安全发现 3 项
| 严重性 | 安全发现 | 位置 |
|---|---|---|
| 提示 | Broad file write capabilities in unittest-completer | sub-skills/unittest-completer/SKILL.md:5 |
| 提示 | Configuration isolation using project hash | scripts/resolve-project.cjs:67 |
| 提示 | Legitimate Jest command execution | scripts/analyze-coverage/index.cjs:41 |
| 资源类型 | 声明权限 | 推断权限 | 状态 | 证据 |
|---|---|---|---|---|
| 文件系统 | READ,WRITE | READ,WRITE | ✓ 一致 | unittest-completer/SKILL.md declares Write/Edit for test file creation; unittest… |
| 命令执行 | WRITE | WRITE | ✓ 一致 | Bash tool declared in all sub-skills; used to run `npx jest` commands which is e… |
| 网络访问 | NONE | NONE | — | No network requests found; only runs local Jest commands |
| 环境变量 | NONE | NONE | — | No sensitive environment variable access or exfiltration |
| 数据库 | NONE | NONE | — | No database access |
| 剪贴板 | NONE | NONE | — | No clipboard access |
目录结构
13 文件 · 57.7 KB · 1699 行 JavaScript 6f · 1017L
Markdown 6f · 677L
JSON 1f · 5L
├─
▾
scripts
│ ├─
guard-config.cjs
JavaScript
│ ├─
reload.cjs
JavaScript
│ └─
resolve-project.cjs
JavaScript
├─
▾
sub-skills
│ ├─
▾
unittest-checker
│ │ ├─
▾
scripts
│ │ │ └─
▾
analyze-coverage
│ │ │ └─
index.cjs
JavaScript
│ │ └─
SKILL.md
Markdown
│ ├─
▾
unittest-completer
│ │ ├─
▾
scripts
│ │ │ └─
▾
check-coverage-100
│ │ │ ├─
index.cjs
JavaScript
│ │ │ └─
README.md
Markdown
│ │ └─
SKILL.md
Markdown
│ └─
▾
unittest-doctor
│ ├─
▾
scripts
│ │ └─
▾
test-error-reporter
│ │ └─
index.cjs
JavaScript
│ └─
SKILL.md
Markdown
├─
_meta.json
JSON
├─
README.md
Markdown
└─
SKILL.md
Markdown
安全亮点
✓ Comprehensive documentation with SKILL.md files for main skill and all sub-skills
✓ Project configuration isolation prevents cross-project data leakage
✓ Uses .temp/ directory (outside git) for temporary files and coverage reports
✓ No credential harvesting, sensitive path access, or data exfiltration
✓ No base64-encoded payloads, hidden instructions, or obfuscated code
✓ Clear error handling with specific error types (config_error, env_error, test_error)
✓ Legitimate subprocess usage for running Jest tests - documented and necessary
✓ Jest configuration parsing uses regex extraction - no unsafe eval()
✓ No external network requests except `npx jest --version` for version detection