Loading the registry…
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; 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.
4 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- in_the_dark_new
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
0 findings · 0.5s
v2.0.11
20 findings · 7.1s
v0.3.74
2 findings · 2.7s
v0.1.0
0 findings · 2.8s
v0.1.0
0 findings · 2.8s
v0.71.0
84 findings · 0.2s
v2.3.8
87 findings · 6.8s
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 · 1.6s
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 22, 2026 | Flagged40 | — | 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 193 findings across every scanner that examined this package. None of the 4 findings rated critical by their scanner were dismissed.
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
6 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/src/SKILL.md, /repo/assets/SKILL.md and 3 more · reported by cisco-skill-scanner
6 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/src/SKILL.md, /repo/assets/SKILL.md and 3 more · reported by cisco-skill-scanner
4 GHSA-5p4m-2wfm-xmqj
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
4 LOW_ANALYZABILITY
Files: /repo/src/screens, /repo/src/screens/game, /repo/src and 1 more · reported by cisco-skill-scanner
4 YARA_prompt_injection_unicode_steganography
Files: /repo/assets/icon_1024.png, /repo/assets/splash.png · reported by cisco-skill-scanner
3 CVE-2026-48779
Files: package-lock.json · reported by trivy
3 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-96hv-2xvq-fx4p
Files: /repo/package-lock.json · reported by osv-scanner
2 CVE-2025-5889
Files: package-lock.json · reported by trivy
2 CVE-2025-64718
Files: package-lock.json · reported by trivy
2 CVE-2026-13149
Files: package-lock.json · reported by trivy
2 CVE-2026-14257
Files: package-lock.json · reported by trivy
2 CVE-2026-26996
Files: package-lock.json · reported by trivy
2 CVE-2026-27903
Files: package-lock.json · reported by trivy
2 CVE-2026-27904
Files: package-lock.json · reported by trivy
2 CVE-2026-33671
Files: package-lock.json · reported by trivy
2 CVE-2026-33672
Files: package-lock.json · reported by trivy
2 CVE-2026-33750
Files: package-lock.json · reported by trivy
2 CVE-2026-53550
Files: package-lock.json · reported by trivy
2 CVE-2026-59869
Files: package-lock.json · reported by trivy
2 CVE-2026-69152
Files: package-lock.json · reported by trivy
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r292-9mhp-454m
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-12816
Files: package-lock.json · reported by trivy
1 CVE-2025-64756
Files: package-lock.json · reported by trivy
1 CVE-2025-66030
Files: package-lock.json · reported by trivy
1 CVE-2025-66031
Files: package-lock.json · reported by trivy
1 CVE-2025-69873
Files: package-lock.json · reported by trivy
1 CVE-2025-71329
Files: package-lock.json · reported by trivy
1 CVE-2025-71330
Files: package-lock.json · reported by trivy
1 CVE-2025-7339
Files: package-lock.json · reported by trivy
1 CVE-2026-12151
Files: package-lock.json · reported by trivy
1 CVE-2026-13311
Files: package-lock.json · reported by trivy
1 CVE-2026-15157
Files: package-lock.json · reported by trivy
1 CVE-2026-1525
Files: package-lock.json · reported by trivy
1 CVE-2026-1526
Files: package-lock.json · reported by trivy
1 CVE-2026-1527
Files: package-lock.json · reported by trivy
1 CVE-2026-1528
Files: package-lock.json · reported by trivy
1 CVE-2026-16728
Files: package-lock.json · reported by trivy
1 CVE-2026-16729
Files: package-lock.json · reported by trivy
1 CVE-2026-22036
Files: package-lock.json · reported by trivy
1 CVE-2026-2229
Files: package-lock.json · reported by trivy
1 CVE-2026-23745
Files: package-lock.json · reported by trivy
1 CVE-2026-23950
Files: package-lock.json · reported by trivy
1 CVE-2026-24842
Files: package-lock.json · reported by trivy
1 CVE-2026-26960
Files: package-lock.json · reported by trivy
1 CVE-2026-29786
Files: package-lock.json · reported by trivy
1 CVE-2026-31802
Files: package-lock.json · reported by trivy
1 CVE-2026-33891
Files: package-lock.json · reported by trivy
1 CVE-2026-33894
Files: package-lock.json · reported by trivy
1 CVE-2026-33895
Files: package-lock.json · reported by trivy
1 CVE-2026-33896
Files: package-lock.json · reported by trivy
1 CVE-2026-34601
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-41672
Files: package-lock.json · reported by trivy
1 CVE-2026-41673
Files: package-lock.json · reported by trivy
1 CVE-2026-41674
Files: package-lock.json · reported by trivy
1 CVE-2026-41675
Files: package-lock.json · reported by trivy
1 CVE-2026-41907
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-45736
Files: package-lock.json · reported by trivy
1 CVE-2026-49356
Files: package-lock.json · reported by trivy
1 CVE-2026-53655
Files: package-lock.json · reported by trivy
1 CVE-2026-59871
Files: package-lock.json · reported by trivy
1 CVE-2026-59873
Files: package-lock.json · reported by trivy
1 CVE-2026-59874
Files: package-lock.json · reported by trivy
1 CVE-2026-59875
Files: package-lock.json · reported by trivy
1 CVE-2026-67213
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
Files: package-lock.json · reported by trivy
1 CVE-2026-6733
Files: package-lock.json · reported by trivy
1 CVE-2026-69153
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 CVE-2026-9277
Files: package-lock.json · reported by trivy
1 CVE-2026-9679
Files: package-lock.json · reported by trivy
1 GHSA-2328-f5f3-gj25
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-23hp-3jrh-7fpw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v35-w6hq-6mfw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-34x7-hfp2-rc4v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35p6-xmwp-9g52
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-554w-wpv2-vw27
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5gfm-wpxj-wjgq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5m6q-g25r-mvwx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p2g-fcmc-qvqq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-65ch-62r8-g69g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-76c9-3jph-rj3q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-83g3-92jg-28cx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f269-vfmq-vjvj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f6ww-3ggp-fr8h
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-gvwx-54wh-qm9j
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j759-j44w-7fr8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p88m-4jfj-68fv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-ppp5-5v6c-4jwp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q67f-28xg-22rw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qffp-2rhf-9h96
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vrm6-8vpv-qv8q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w3rx-r6r6-pgpr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wh4c-j3r5-mjhp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-x6wf-f3px-wcqx
Files: /repo/package-lock.json · reported by osv-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-11525
Files: package-lock.json · reported by trivy
Critical dependency vulnerabilities and low code analyzability detected.
The artifact contains critical vulnerabilities in its dependencies, identified in `package-lock.json`, which could introduce significant risks. Additionally, several parts of the installed code, including `/repo`, `/repo/src`, and subdirectories, exhibit low analyzability. This condition makes it difficult to assess potential risks such as shell execution or network egress that might be present in these sections. These findings warrant immediate attention prior to deployment.
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.
Showing 25 of 114; the rest are in the per-scanner reports above.