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.
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 -- umm
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
21 findings · 10.2s
v0.3.74
13 findings · 5.0s
v0.1.0
21 findings · 6.0s
v0.1.0
0 findings · 6.1s
v0.71.0
84 findings · 0.6s
v2.3.8
141 findings · 10.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
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 | Flagged21 | — | 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 280 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 72 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.
12 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/app/api/integrations/discord/callback/route.ts, /repo/src/app/api/integrations/google_calendar/callback/route.ts, /repo/src/app/api/integrations/slack/callback/route.ts and 1 more · reported by nerlo-behavioral
9 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/app/api/integrations/discord/callback/route.ts, /repo/src/app/api/integrations/google_calendar/callback/route.ts, /repo/src/app/api/integrations/slack/callback/route.ts and 1 more · reported by nerlo-behavioral
4 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-8h8q-6873-q5fj
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-f88m-g3jw-g9cj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-h25m-26qc-wcjf
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml, package-lock.json and 1 more · reported by osv-scanner, trivy
4 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-q4gf-8mx6-v5v3
Files: package-lock.json, pnpm-lock.yaml, /repo/package-lock.json and 1 more · reported by trivy, osv-scanner
4 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
3 AAK-SECRET-004
Files: src/lib/supabase/client.ts, src/lib/supabase/middleware.ts, src/lib/supabase/server.ts · reported by agent-audit-kit
2 CVE-2025-59472
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27977
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27978
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27979
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-27980
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-29057
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44572
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44573
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44574
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44575
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44576
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44577
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44578
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44579
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44581
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-44582
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-45109
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-45623
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64641
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64642
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64643
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64645
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64647
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64648
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-64649
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-67213
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-67214
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-69153
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 CVE-2026-73646
Files: package-lock.json, pnpm-lock.yaml · reported by trivy
2 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-267c-6grr-h53f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-26hh-7cqf-hhc6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-36qx-fr4f-26g5
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3g8h-86w9-wvmq
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4633-3j49-mh5q
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-492v-c6pp-mqqv
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4c39-4ccg-62r3
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-4x5r-pxfx-6jf8
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5f7q-jpqc-wp7h
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-6gpp-xcg3-4w24
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-89xv-2m56-2m9x
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-955p-x3mx-jcvp
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-9g9p-9gw9-jx7f
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c4j6-fc7j-m34r
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-gx5p-jg67-6x7h
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h64f-5h5j-jqjh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-jcc7-9wpm-mj36
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-m99w-x7hq-7vfj
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mg66-mrh9-m8jx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mq59-m269-xvcx
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p9j2-gv94-2wf4
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q8wf-6r8g-63ch
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-vfv6-92ff-j949
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-w37m-7fhw-fmv9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-w5hq-g745-h8pq
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wfc6-r584-vfw7
Files: /repo/package-lock.json, /repo/pnpm-lock.yaml · 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-2026-45736
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-49356
Files: pnpm-lock.yaml · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
70 The review call did not complete.
Rules: LOW_ANALYZABILITY, GHSA-mwv6-3258-q52c, CVE-2026-48779 and 20 more · Files: /repo, package-lock.json, pnpm-lock.yaml and 15 more · reported by cisco-skill-scanner, trivy, osv-scanner and 1 more
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Exposes credentials, performs network egress, and has vulnerable dependencies.
The artifact exposes credentials in Supabase client, middleware, and server configurations. It performs network egress of secrets within integration callback routes for Discord, Google Calendar, and Slack, as well as sync routes. Additionally, the artifact includes numerous high-severity vulnerabilities in its dependencies, identified in the package-lock.json.
Concern level assessed by the review: High. 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.