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.
5 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 -- morph-app
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.7s
v2.0.11
23 findings · 8.1s
v0.3.74
2 findings · 1.9s
v0.1.0
1 finding · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
118 findings · 0.3s
v2.3.8
160 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 · 1.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 | 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 304 findings across every scanner that examined this package. None of the 5 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 54 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.
4 GHSA-42h9-826w-cgv3
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml, client/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-7q8q-rj6j-mhjq
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml, client/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-jqh4-m9w3-8hp9
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml, /repo/client/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 GHSA-mmx7-hfxf-jppx
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml, /repo/client/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 GHSA-pmv8-rq9r-6j72
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml, client/pnpm-lock.yaml and 1 more · reported by osv-scanner, trivy
4 GHSA-r4q5-vmmm-2653
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml, /repo/client/pnpm-lock.yaml and 1 more · reported by trivy, osv-scanner
4 UNANALYZABLE_BINARY
Files: /repo/client/public/sounds/start.mp3, /repo/client/public/sounds/ring.mp3, /repo/client/public/sounds/reset.mp3 and 1 more · reported by cisco-skill-scanner
3 CVE-2026-45736
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
3 CVE-2026-48779
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
3 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-58qx-3vcg-4xpx
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-96hv-2xvq-fx4p
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 AAK-LEGAL-002
Files: client/package.json, .vite/deps/package.json · reported by agent-audit-kit
2 CVE-2025-58754
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2025-62718
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2025-7783
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-12143
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-25639
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-33151
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-34077
Files: client/pnpm-lock.yaml · reported by trivy
2 CVE-2026-40175
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42033
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42034
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42035
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42036
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42037
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42038
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42039
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42041
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42042
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42043
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42044
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-42264
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44486
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44487
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44488
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44490
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44494
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44495
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-44496
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 CVE-2026-69185
Files: client/pnpm-lock.yaml, server/pnpm-lock.yaml · reported by trivy
2 GHSA-2m8v-j782-fhvr
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-35jp-ww65-95wh
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3g43-6gmg-66jw
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3p68-rc4w-qgx5
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3w6x-2g7m-8v23
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-43fc-jf86-j433
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-445q-vr5w-6q77
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4hjh-wcwx-xvwj
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5c9x-8gcm-mpgx
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-62hf-57xw-28j9
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-677m-j7p3-52f9
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6chq-wfr3-2hj9
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-777c-7fjr-54vf
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-898c-q2cr-xwhg
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f23m-r3pf-42rh
Files: /repo/client/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fjxv-7rqg-78g4
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-fvcv-3m26-pcqx
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hfxv-24rg-xrqf
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hmw2-7cc7-3qxx
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j5f8-grm9-p9fc
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m7pr-hjqh-92cm
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p92q-9vqr-4j8v
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pf86-5x62-jrwf
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-pmwg-cvhr-8vh7
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8qp-cvcw-x6jj
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r5fr-rjxr-66jc
Files: /repo/client/pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rxv8-25v2-qmq8
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vf2m-468p-8v99
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w9j2-pvgh-6h63
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-xx6v-rp6x-q39c
Files: /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml · reported by osv-scanner
1 CVE-2025-15284
Files: server/pnpm-lock.yaml · reported by trivy
1 CVE-2025-27152
Files: server/pnpm-lock.yaml · reported by trivy
1 CVE-2025-30208
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-31125
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-31486
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-43864
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-43865
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-59057
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-62522
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2025-68470
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-21884
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-22029
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27606
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-39363
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-39365
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-40181
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-42211
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-42342
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-4867
Files: server/pnpm-lock.yaml · reported by trivy
1 CVE-2026-53571
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-53666
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-55685
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59725
Files: server/pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: client/pnpm-lock.yaml · reported by trivy
1 CVE-2026-8723
Files: server/pnpm-lock.yaml · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2w69-qvjg-hvjx
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-356w-63v5-8wf4
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-37ch-88jc-xwx2
Files: /repo/server/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-395f-4hp3-45gv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3cgp-3xvw-98x8
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-49rj-9fvp-4h2h
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
Files: /repo/server/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-859w-5945-r5v3
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8v8x-cx79-35w7
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x6r-g9mw-2r78
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-968p-4wvh-cqc8
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9jcx-v3wj-wh4m
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-chx6-hx7r-mcp5
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-cpj6-fhp6-mr6j
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f46r-rw29-r322
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h5cw-625j-3rxh
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jr5f-v2jv-69x6
Files: /repo/server/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r635-g3xr-vw7x
Files: /repo/server/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/client/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
44 The review budget for this scan was already spent before these findings were reached.
Rules: CVE-2026-2950, CVE-2026-53669, GHSA-wrjc-x8rr-h8h6 and 33 more · Files: client/pnpm-lock.yaml, /repo/client/pnpm-lock.yaml, /repo/server/pnpm-lock.yaml and 10 more · reported by trivy, osv-scanner, cisco-skill-scanner and 1 more
10 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_NETWORK · Files: /repo/client/src/hooks/use-activity.ts, /repo/client/src/hooks/use-room.ts, /repo/client/src/hooks/use-quote.ts and 1 more · reported by cisco-skill-scanner
Critical vulnerabilities found in dependencies.
This artifact contains critical vulnerabilities in its dependencies, identified in `pnpm-lock.yaml` files for both client and server components. These critical findings, such as GHSA-fjxv-7rqg-78g4, GHSA-w7jw-789q-3m8p, and CVE-2025-7783, could enable remote code execution or unauthorized data access within the artifact's environment. Additionally, numerous high-severity vulnerabilities are present across various dependency files, requiring further investigation.
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 25; the rest are in the per-scanner reports above.