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 -- ayussh-2/grid-sense
6 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.
v2.0.11
76 findings · 8.4s
v0.3.74
1 finding · 2.2s
v0.1.0
0 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.71.0
53 findings · 0.3s
v2.3.8
62 findings · 8.0s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.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 · 0.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 22, 2026 | Flagged37 | — | agentshield ·n/a: not applicablecisco-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 192 findings across every scanner that examined this package.
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.
50 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: DATA_EXFIL_NETWORK_REQUESTS · Files: /repo/server/tests/simulation_test.py · reported by cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
6 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/server/services/pathway/utils.py · reported by cisco-skill-scanner
6 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/server/routes/websocket.py, /repo/server/services/devices.py, /repo/server/services/grid_context.py · reported by cisco-skill-scanner
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/server/SKILL.md, /repo/client/SKILL.md · reported by cisco-skill-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/server/SKILL.md, /repo/client/SKILL.md · reported by cisco-skill-scanner
2 DATA_EXFIL_JS_NETWORK
Files: /repo/client/src/lib/api/client.ts · reported by cisco-skill-scanner
2 GHSA-4xgf-cpjx-pc3j
Files: /repo/server/requirements.txt, server/requirements.txt · reported by osv-scanner, trivy
2 GHSA-6g55-p6wh-862q
Files: /repo/client/bun.lock · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: client/bun.lock, /repo/client/bun.lock · reported by trivy, osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/client/bun.lock · reported by osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: client/bun.lock, /repo/client/bun.lock · reported by trivy, osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/client/bun.lock · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/client/bun.lock · reported by osv-scanner
2 HIDDEN_DATA_FILE
Files: /repo/client/.sample.env · reported by cisco-skill-scanner
2 LOW_ANALYZABILITY
Files: /repo, /repo/client · reported by cisco-skill-scanner
2 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md, /repo/server/repo/server/README.md · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: client/package.json · reported by agent-audit-kit
1 CVE-2026-27977
Files: client/bun.lock · reported by trivy
1 CVE-2026-27978
Files: client/bun.lock · reported by trivy
1 CVE-2026-27979
Files: client/bun.lock · reported by trivy
1 CVE-2026-27980
Files: client/bun.lock · reported by trivy
1 CVE-2026-28684
Files: server/requirements.txt · reported by trivy
1 CVE-2026-29057
Files: client/bun.lock · reported by trivy
1 CVE-2026-2950
Files: client/bun.lock · reported by trivy
1 CVE-2026-40347
Files: server/requirements.txt · reported by trivy
1 CVE-2026-41305
Files: client/bun.lock · reported by trivy
1 CVE-2026-42561
Files: server/requirements.txt · reported by trivy
1 CVE-2026-44431
Files: server/requirements.txt · reported by trivy
1 CVE-2026-44432
Files: server/requirements.txt · reported by trivy
1 CVE-2026-44572
Files: client/bun.lock · reported by trivy
1 CVE-2026-44573
Files: client/bun.lock · reported by trivy
1 CVE-2026-44574
Files: client/bun.lock · reported by trivy
1 CVE-2026-44575
Files: client/bun.lock · reported by trivy
1 CVE-2026-44576
Files: client/bun.lock · reported by trivy
1 CVE-2026-44577
Files: client/bun.lock · reported by trivy
1 CVE-2026-44578
Files: client/bun.lock · reported by trivy
1 CVE-2026-44579
Files: client/bun.lock · reported by trivy
1 CVE-2026-44580
Files: client/bun.lock · reported by trivy
1 CVE-2026-44581
Files: client/bun.lock · reported by trivy
1 CVE-2026-44582
Files: client/bun.lock · reported by trivy
1 CVE-2026-45109
Files: client/bun.lock · reported by trivy
1 CVE-2026-4539
Files: server/requirements.txt · reported by trivy
1 CVE-2026-45409
Files: server/requirements.txt · reported by trivy
1 CVE-2026-45623
Files: client/bun.lock · reported by trivy
1 CVE-2026-4800
Files: client/bun.lock · reported by trivy
1 CVE-2026-48710
Files: server/requirements.txt · reported by trivy
1 CVE-2026-48817
Files: server/requirements.txt · reported by trivy
1 CVE-2026-48818
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53537
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53538
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53539
Files: server/requirements.txt · reported by trivy
1 CVE-2026-53540
Files: server/requirements.txt · reported by trivy
1 CVE-2026-54283
Files: server/requirements.txt · reported by trivy
1 CVE-2026-64641
Files: client/bun.lock · reported by trivy
1 CVE-2026-64642
Files: client/bun.lock · reported by trivy
1 CVE-2026-64643
Files: client/bun.lock · reported by trivy
1 CVE-2026-64644
Files: client/bun.lock · reported by trivy
1 CVE-2026-64645
Files: client/bun.lock · reported by trivy
1 CVE-2026-64646
Files: client/bun.lock · reported by trivy
1 CVE-2026-64647
Files: client/bun.lock · reported by trivy
1 CVE-2026-64648
Files: client/bun.lock · reported by trivy
1 CVE-2026-64649
Files: client/bun.lock · reported by trivy
1 CVE-2026-67213
Files: client/bun.lock · reported by trivy
1 CVE-2026-67214
Files: client/bun.lock · reported by trivy
1 CVE-2026-69153
Files: client/bun.lock · reported by trivy
1 CVE-2026-73646
Files: client/bun.lock · reported by trivy
1 GHSA-267c-6grr-h53f
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-26hh-7cqf-hhc6
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-492v-c6pp-mqqv
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-6gpp-xcg3-4w24
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-c4j6-fc7j-m34r
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-f88m-g3jw-g9cj
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-ffhc-5mcf-pf4q
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-h27x-g6w4-24gq
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-jcc7-9wpm-mj36
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-mg66-mrh9-m8jx
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-mq59-m269-xvcx
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-q8wf-6r8g-63ch
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-vfv6-92ff-j949
Files: /repo/client/bun.lock · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/client/bun.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-142
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1873
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/server/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/server/requirements.txt · reported by osv-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-54282
Files: server/requirements.txt · reported by trivy
Critical resource abuse and supply chain vulnerabilities
The artifact contains multiple high-severity vulnerabilities, including potential resource abuse due to infinite loops in server-side components like `websocket.py`, `devices.py`, and `grid_context.py`. Numerous high-severity supply chain vulnerabilities are present in client-side dependencies, as indicated by GHSA and CVE findings in `bun.lock`. Additionally, parts of the code exhibit low analyzability, which may obscure further issues.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 58; 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.