Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
2 critical findings reported by osv-scanner, 1 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- electron-texture-bridge
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- electron-texture-bridge ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
2 findings · 1.0s
v2.0.11
92 findings · 11.8s
v0.3.74
4 findings · 3.6s
v0.1.0
0 findings · 4.2s
v0.1.0
7 findings · 4.2s
v0.71.0
35 findings · 0.4s
v2.3.8
197 findings · 8.0s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged34 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 337 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 143 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
27 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: opt.nerlo-rules.nerlo-install-pipe-to-shell, PIPELINE_TAINT_FLOW, GHSA-2v37-7h3g-55p8 and 17 more · Files: /repo/docs/INSTALLATION.md, /repo/docs/ja/INSTALLATION.md, /repo/packages/example/pnpm-lock.yaml · reported by nerlo-install-instruction, cisco-skill-scanner, osv-scanner
4 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: LOW_ANALYZABILITY, FILE_MAGIC_MISMATCH · Files: /repo/packages/renderer/src/__tests__, /repo/packages/core/src/__tests__/electron-free-guard.test.ts · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
8 GHSA-23c5-xmqv-rm74
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
8 GHSA-3ppc-4f35-3m26
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
8 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
6 LOW_ANALYZABILITY
Files: /repo, /repo/packages/core/src, /repo/packages/renderer and 3 more · reported by cisco-skill-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f886-m6hf-6m8v
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
140 The review budget for this scan was already spent before these findings were reached.
Rules: CVE-2026-70607, GHSA-h67p-54hq-rp68, GHSA-xj5x-m3f3-5x3h and 52 more · Files: pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml and 41 more · reported by trivy, osv-scanner, agent-audit-kit and 2 more
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-MARKETPLACE-001, hooks-no-pretooluse · Files: .claude-plugin/marketplace.json, settings.json, .claude/settings.json · reported by agent-audit-kit, agentshield
Critical and high-severity dependency vulnerabilities found.
The artifact includes critical and numerous high-severity vulnerabilities within its dependencies. A critical vulnerability (GHSA-23hp-3jrh-7fpw) and many high-severity dependency issues are identified in `pnpm-lock.yaml` files. These vulnerabilities could enable remote code execution, denial of service, or information disclosure. Additionally, a high-severity finding in `preview-manager.ts` warrants further review.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
4 GHSA-mh99-v99m-4gvg
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-23hp-3jrh-7fpw
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v35-w6hq-6mfw
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4f78-qhmw-8j8m
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-532v-xpq5-8h95
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5rqw-r77c-jp79
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7g7r-gx96-252g
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-83g3-92jg-28cx
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8x88-c5mf-7j5w
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9pf5-hg6p-4pwp
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9ppj-qmqm-q256
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9w97-2464-8783
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9wfr-w7mm-pc7f
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f6ww-3ggp-fr8h
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h7rp-cf8h-j98x
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j759-j44w-7fr8
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-jmr9-qjv8-65gv
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mwp4-54f8-5fhr
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-ph9p-34f9-6g65
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-qffp-2rhf-9h96
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r292-9mhp-454m
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v2v4-37r5-5v8g
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v3j7-r9gq-3gjw
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6wh-96g9-6wx3
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v93f-fgjr-hjrj
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml, /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wh4c-j3r5-mjhp
Files: /repo/packages/example/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2026-34769
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34770
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34771
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34774
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34775
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34776
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34778
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34779
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-34780
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-56876
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70597
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70599
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70601
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70603
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70604
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70605
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70608
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70609
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70611
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-70612
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3c8v-cfp5-9885
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4p4r-m79c-wq3v
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5c9j-mhmv-5xgx
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-737v-mqg7-c878
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8337-3p73-46f4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9f4c-93c8-jc8g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f3pv-wv63-48x8
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ff2p-hmqr-hxm4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jfqg-hf23-qpw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jjp3-mq3x-295m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jm7p-cc5g-qwxx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m55f-7gqj-fr98
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwmh-mq4g-g6gr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p2f4-r6v6-j797
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p2rr-rvmm-c5fp
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2wj-q39q-566r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/packages/example/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x6wf-f3px-wcqx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xj5x-m3f3-5x3h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 UNANALYZABLE_BINARY
Files: /repo/packages/example/build/icon.icns · reported by cisco-skill-scanner
Showing 24 of 24; the rest are in the per-scanner reports above.