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.
2 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 -- chzzk4tv4
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 · 1.3s
v2.0.11
11 findings · 10.5s
v0.3.74
3 findings · 2.7s
v0.1.0
1 finding · 5.5s
v0.1.0
0 findings · 5.5s
v0.71.0
38 findings · 0.3s
v2.3.8
38 findings · 9.9s
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.2s
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 | Flagged37 | — | 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 91 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 8 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
2 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-r4q5-vmmm-2653
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/js/ui/searchManager.js · reported by agent-audit-kit
1 AAK-SPLUNK-TOKLOG-001
Files: ui/watchScreen.js · reported by agent-audit-kit
1 ARCHIVE_FILE_DETECTED
Files: /repo/images-20250604T031152Z-1-001.zip · reported by cisco-skill-scanner
1 CVE-2025-15284
Files: package-lock.json · reported by trivy
1 CVE-2025-58754
Files: package-lock.json · reported by trivy
1 CVE-2025-59343
Files: package-lock.json · reported by trivy
1 CVE-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2025-7783
Files: package-lock.json · reported by trivy
1 CVE-2026-12143
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-2391
Files: package-lock.json · reported by trivy
1 CVE-2026-25639
Files: package-lock.json · reported by trivy
1 CVE-2026-40175
Files: package-lock.json · reported by trivy
1 CVE-2026-42033
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42035
Files: package-lock.json · reported by trivy
1 CVE-2026-42036
Files: package-lock.json · reported by trivy
1 CVE-2026-42037
Files: package-lock.json · reported by trivy
1 CVE-2026-42038
Files: package-lock.json · reported by trivy
1 CVE-2026-42039
Files: package-lock.json · reported by trivy
1 CVE-2026-42040
Files: package-lock.json · reported by trivy
1 CVE-2026-42041
Files: package-lock.json · reported by trivy
1 CVE-2026-42042
Files: package-lock.json · reported by trivy
1 CVE-2026-42043
Files: package-lock.json · reported by trivy
1 CVE-2026-42044
Files: package-lock.json · reported by trivy
1 CVE-2026-42264
Files: package-lock.json · reported by trivy
1 CVE-2026-44486
Files: package-lock.json · reported by trivy
1 CVE-2026-44487
Files: package-lock.json · reported by trivy
1 CVE-2026-44488
Files: package-lock.json · reported by trivy
1 CVE-2026-44490
Files: package-lock.json · reported by trivy
1 CVE-2026-44494
Files: package-lock.json · reported by trivy
1 CVE-2026-44495
Files: package-lock.json · reported by trivy
1 CVE-2026-44496
Files: package-lock.json · reported by trivy
1 CVE-2026-4867
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-37ch-88jc-xwx2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3g43-6gmg-66jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-43fc-jf86-j433
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-445q-vr5w-6q77
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4hjh-wcwx-xvwj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-62hf-57xw-28j9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-777c-7fjr-54vf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fjxv-7rqg-78g4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hfxv-24rg-xrqf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p92q-9vqr-4j8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pf86-5x62-jrwf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8qp-cvcw-x6jj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vj76-c3g6-qr5v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/js/api/chzzk.js · reported by nerlo-behavioral
1 UNANALYZABLE_BINARY
Files: /repo/images-20250604T031152Z-1-001.zip · reported by cisco-skill-scanner
8 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_NETWORK, HIDDEN_DATA_FILE, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: /repo/src/js/api/chzzk.js, /repo/.aresignore, /repo/SKILL.md and 1 more · reported by cisco-skill-scanner
Critical dependency vulnerabilities and secret exfiltration risks.
The artifact includes critical vulnerabilities in its dependencies, as indicated in `package-lock.json`. High-severity findings reveal potential credential exposure in `src/js/ui/searchManager.js` and `ui/watchScreen.js`. Additionally, secrets are sent over the network from `src/js/api/chzzk.js`, and other network egress for data exfiltration is present.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 23 of 23; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.