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 -- shopify-nextjs
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
6 findings · 6.6s
v0.3.74
2 findings · 3.3s
v0.1.0
0 findings · 3.4s
v0.1.0
0 findings · 3.4s
v0.71.0
42 findings · 0.5s
v2.3.8
103 findings · 8.1s
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 | Flagged44 | — | 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 153 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 60 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-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5j98-mcp5-4vw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 CVE-2024-47831
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-55565
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2024-56332
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-27789
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-29927
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-32421
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-48068
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-55173
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-57752
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-59471
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27980
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29057
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44572
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44576
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44577
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44581
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44582
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-49356
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64647
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64648
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3h52-269p-cp9r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4342-x723-ch2f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52f5-9888-hmc6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-73rr-hh4g-fpgx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7gfc-8cq8-jh5f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7m27-7ghc-44w9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8h8q-6873-q5fj
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-955p-x3mx-jcvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9g9p-9gw9-jx7f
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-f6v4-cf5j-vf3w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f82v-jwr5-mffw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ffhc-5mcf-pf4q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fjxv-7rqg-78g4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g5qg-72qw-gw5v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g77x-44xx-532m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwcw-c2x4-8c55
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwv6-3258-q52c
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-p9j2-gv94-2wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ph9p-34f9-6g65
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qpjv-v59x-3qc4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vfv6-92ff-j949
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vpq2-c234-7xj6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7jw-789q-3m8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wf6x-7x77-mvgw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
56 The review call did not complete.
Rules: CVE-2024-46982, GHSA-8h8q-6873-q5fj, CVE-2024-51479 and 44 more · Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml, src/services/shopify/shopify-admin.ts and 2 more · reported by trivy, osv-scanner, agent-audit-kit and 1 more
4 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_NETWORK, SOCIAL_ENG_VAGUE_DESCRIPTION, HIDDEN_DATA_FILE and 1 more · Files: /repo/src/services/shopify/shopify-base.ts, /repo/SKILL.md, /repo/.nvim/config.json · reported by cisco-skill-scanner
Critical vulnerabilities, exposed credentials, and executable scripts found.
The artifact contains multiple critical vulnerabilities identified in its dependencies, primarily within `pnpm-lock.yaml`. A high-severity finding indicates an exposed secret in `src/services/shopify/shopify-admin.ts`, posing a direct risk of credential access. Furthermore, a hidden executable script in `.graphqlrc.ts` suggests potential for shell execution. The overall low analyzability of the repository also raises concerns regarding hidden risks.
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 78; the rest are in the per-scanner reports above.