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.
3 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 -- use-reducer-practice
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.6s
v2.0.11
7 findings · 8.2s
v0.3.74
2 findings · 2.1s
v0.1.0
2 findings · 3.9s
v0.1.0
0 findings · 3.9s
v0.71.0
40 findings · 0.2s
v2.3.8
97 findings · 7.2s
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 · 2.0s
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 | Flagged42 | — | 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 148 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 30 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.
1 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: FILE_MAGIC_MISMATCH · Files: /repo/__tests__/formatCurrency.test.js · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
3 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
2
25 The review call did not complete.
Rules: LOW_ANALYZABILITY, GHSA-8h8q-6873-q5fj, GHSA-83g3-92jg-28cx and 20 more · Files: /repo, package-lock.json, /repo/package-lock.json and 1 more · reported by cisco-skill-scanner, trivy, osv-scanner and 1 more
5 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_NETWORK, FILE_MAGIC_MISMATCH, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: /repo/app/promise-and-async-confirm/mutation.ts, /repo/app/react-window-practice/page.tsx, /repo/jest.setup.js and 1 more · reported by cisco-skill-scanner
Critical vulnerabilities and secret egress detected
Critical vulnerabilities are present in the artifact's dependencies, identified in `package-lock.json`. A behavioral finding indicates potential network egress of secrets from `/repo/app/react-window-practice/page.tsx`. Additionally, numerous high-severity vulnerabilities are present in other dependencies. The artifact also exhibits low analyzability, which may impede comprehensive security 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.
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
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-f23m-r3pf-42rh
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-h25m-26qc-wcjf
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
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-mwv6-3258-q52c
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r5fr-rjxr-66jc
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-w37m-7fhw-fmv9
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-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-13465
Files: package-lock.json · reported by trivy
1 CVE-2025-55173
Files: package-lock.json · reported by trivy
1 CVE-2025-55182
Files: package-lock.json · reported by trivy
1 CVE-2025-57752
Files: package-lock.json · reported by trivy
1 CVE-2025-57822
Files: package-lock.json · reported by trivy
1 CVE-2025-59471
Files: package-lock.json · reported by trivy
1 CVE-2026-27980
Files: package-lock.json · reported by trivy
1 CVE-2026-29057
Files: package-lock.json · reported by trivy
1 CVE-2026-2950
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-44572
Files: package-lock.json · reported by trivy
1 CVE-2026-44575
Files: package-lock.json · reported by trivy
1 CVE-2026-44576
Files: package-lock.json · reported by trivy
1 CVE-2026-44577
Files: package-lock.json · reported by trivy
1 CVE-2026-44579
Files: package-lock.json · reported by trivy
1 CVE-2026-44580
Files: package-lock.json · reported by trivy
1 CVE-2026-44581
Files: package-lock.json · reported by trivy
1 CVE-2026-44582
Files: package-lock.json · reported by trivy
1 CVE-2026-45109
Files: package-lock.json · reported by trivy
1 CVE-2026-64643
Files: package-lock.json · reported by trivy
1 CVE-2026-64645
Files: package-lock.json · reported by trivy
1 CVE-2026-64646
Files: package-lock.json · reported by trivy
1 CVE-2026-64647
Files: package-lock.json · reported by trivy
1 CVE-2026-64648
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
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 GHSA-23hp-3jrh-7fpw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-25h7-pfq9-p65f
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-34x7-hfp2-rc4v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4342-x723-ch2f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
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-58qx-3vcg-4xpx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
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-955p-x3mx-jcvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9g9p-9gw9-jx7f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9qr9-h5gf-34mp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-ffhc-5mcf-pf4q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g5qg-72qw-gw5v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
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-gx5p-jg67-6x7h
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mg66-mrh9-m8jx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r292-9mhp-454m
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-vfv6-92ff-j949
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-w8wr-v893-vjvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xffm-g5w8-qvg7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xv57-4mr9-wg8v
Files: /repo/package-lock.json · reported by osv-scanner
1 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/app/promise-and-async-confirm/mutation.ts · reported by nerlo-behavioral
Showing 23 of 23; the rest are in the per-scanner reports above.