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 -- mehmetakifemre/solveaihackhathon31
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
8 findings · 7.2s
v0.3.74
1 finding · 1.4s
v0.1.0
1 finding · 3.0s
v0.1.0
0 findings · 3.0s
v0.71.0
29 findings · 0.2s
v2.3.8
37 findings · 6.8s
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 21, 2026 | Flagged41 | — | 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 76 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.
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md · 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.
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/frontend/package-lock.json · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: frontend/package-lock.json, /repo/frontend/package-lock.json · reported by trivy, osv-scanner
2 GHSA-f88m-g3jw-g9cj
Files: /repo/frontend/package-lock.json, frontend/package-lock.json · reported by osv-scanner, trivy
2 GHSA-mh99-v99m-4gvg
Files: /repo/frontend/package-lock.json · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/frontend/package-lock.json · reported by osv-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/backend/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/backend/SKILL.md
Critical vulnerabilities, including secret network egress, found in artifact.
The artifact contains multiple high-severity vulnerabilities in its dependencies, primarily affecting the frontend component. A critical behavioral finding indicates that secrets may be transmitted over the network from `/repo/frontend/lib/api.ts`. Additionally, the overall analyzability of the code is low, which could obscure further 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.
1 AAK-LEGAL-002
Files: frontend/package.json · reported by agent-audit-kit
1 CVE-2026-41305
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44572
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44573
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44574
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44575
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44576
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44577
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44578
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44579
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44580
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44581
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-44582
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-45109
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-45623
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64641
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64642
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64643
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64644
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64645
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64646
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64647
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64648
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64649
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-67213
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-67214
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-69153
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-73646
Files: frontend/package-lock.json · reported by trivy
1 DATA_EXFIL_JS_NETWORK
Files: /repo/frontend/lib/api.ts · reported by cisco-skill-scanner
1 GHSA-267c-6grr-h53f
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-26hh-7cqf-hhc6
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-492v-c6pp-mqqv
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-6gpp-xcg3-4w24
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-c4j6-fc7j-m34r
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-ffhc-5mcf-pf4q
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-jxxr-4gwj-5jf2
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-mg66-mrh9-m8jx
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-q8wf-6r8g-63ch
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-vfv6-92ff-j949
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/frontend/lib/api.ts · reported by nerlo-behavioral
Showing 25 of 40; the rest are in the per-scanner reports above.