setup-ts-deep-modules
Verdict safe, but 1 finding (1 info), mainly policy violation. Most recent scan 2026-10-22.
Second scanner: NVIDIA SkillSpector
SkillSpector found no issues but could not fully inspect the package, usually because SKILL.md refers to a file that is not present, so it fails closed to CAUTION instead of SAFE. Read it as "not fully checked", not as a finding. How the two scanners compare across the whole corpus: Two scanners, one corpus.
What this skill does
Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.
- Package
- 3 files, 11 KB
- SKILL.md
- 1077 words, 11 sections
- Code
- JavaScript (1)
SKILL.md covers: Setup TS Deep Modules · The shape this enforces · Steps · 1. Detect the environment · 2. Install dependency-cruiser · 3. Write the config · 4. Wire it into the checks · 5. Scaffold the example package · 6. Prove the rules bite · 7. Document the convention · Notes
Findings
INFO Skill does not specify a license Policy Violationstatic
Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.
SKILL.md
What is in the package
| File | Kind | Size |
|---|---|---|
SKILL.md | doc | 7.4 KB |
dependency-cruiser.config.cjs | script | 3.6 KB |
agents/openai.yaml | config | 149 B |
External hosts referenced
github.com
Hostnames that appear in the skill's files. Referencing a host is not a finding; compare against the findings above and the skill's stated purpose.
Package contents recorded 2026-10-22 at commit 5beb35b040e3. The scan above ran against the version current at scan time; the two can differ if the skill has since been updated.
What we checked
- Static analyzer. Pattern rules over SKILL.md and bundled files: known-bad commands, exfiltration URLs, secrets, obfuscation.
- Bytecode analyzer.
- Pipeline analyzer.
- Correlation analyzer.
- Behavioral analyzer. Checks what the skill asks the agent to do against what its description claims it does.
- Trigger analyzer. Looks for instructions that fire on conditions the user did not ask for.
What we did not check
- Runtime behaviour. The skill was not executed; findings come from reading its files.
- Anything fetched at install or run time, including remote scripts, package dependencies, and URLs the skill tells the agent to open.
- Content the analyzers cannot read: images, binaries, and some non-English text.
- Known scanner bypass classes. See the methodology and limitations page.
Sources
- Repository: https://github.com/mattpocock/skills
- Raw scan result: mattpocock-skills-skills-in-progress-setup-ts-deep-modules-scan.json
- Badge for your README:
- Request a re-scan