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 -- bhanuprasanna2001/speare_hack_nation
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
45 findings · 19.8s
v0.3.74
1 finding · 11.5s
v0.1.0
0 findings · 5.1s
v0.1.0
0 findings · 5.1s
v0.71.0
33 findings · 2.4s
v2.3.8
37 findings · 6.4s
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 20, 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 116 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 4 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.
15 UNANALYZABLE_BINARY
Files: /repo/backend/chroma_db/ed610421-248f-4725-9175-6adf141da8ea/data_level0.bin, /repo/backend/chroma_db/c140b2e4-ad10-4019-85e9-ed67b824ae1a/link_lists.bin, /repo/data/SupportMind__Final_Data.xlsx and 12 more · reported by cisco-skill-scanner
14 BINARY_FILE_DETECTED
Files: /repo/data/SupportMind__Final_Data.xlsx!/xl/metadata, /repo/backend/chroma_db/ed610421-248f-4725-9175-6adf141da8ea/link_lists.bin, /repo/backend/chroma_db/854eb26c-a6c5-4cfa-9c8e-20448673ca67/length.bin and 11 more · reported by cisco-skill-scanner
6 FILE_MAGIC_MISMATCH
Files: /repo/backend/chroma_db/854eb26c-a6c5-4cfa-9c8e-20448673ca67/length.bin, /repo/backend/chroma_db/c140b2e4-ad10-4019-85e9-ed67b824ae1a/length.bin, /repo/backend/chroma_db/ed610421-248f-4725-9175-6adf141da8ea/length.bin and 3 more · reported by cisco-skill-scanner
2 ASSET_PROMPT_INJECTION
Files: /repo/data/SupportMind__Final_Data.xlsx!/xl/sharedStrings.xml · reported by cisco-skill-scanner
2 GHSA-6g55-p6wh-862q
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-fxqj-rqcc-2cmp
Files: /repo/frontend/package-lock.json · reported by osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: frontend/package-lock.json, /repo/frontend/package-lock.json · reported by trivy, osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/frontend/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-002
Files: frontend/package.json · reported by agent-audit-kit
1 ARCHIVE_FILE_DETECTED
Files: /repo/data/SupportMind__Final_Data.xlsx · reported by cisco-skill-scanner
1 CVE-2026-27980
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-29057
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-2950
Files: frontend/package-lock.json · reported by trivy
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-4800
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-64641
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 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-3x4c-7xq6-9pq8
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-68g3-v927-f742
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-f23m-r3pf-42rh
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-ggv3-7p47-pfv8
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-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-r5fr-rjxr-66jc
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 HIDDEN_DATA_FILE
Files: /repo/data/SupportMind__Final_Data.xlsx!/_rels/.rels · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 OVERSIZED_FILE
Files: /repo/backend/chroma_db/chroma.sqlite3 · reported by cisco-skill-scanner
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, MANIFEST_MISSING_LICENSE · Files: /repo/frontend/src/lib/api.ts, /repo/SKILL.md · reported by cisco-skill-scanner
Multiple high-severity vulnerabilities and low analyzability
The artifact contains multiple high-severity vulnerabilities within its frontend dependencies, posing various security risks. A high-severity finding also indicates low analyzability of the repository, which hinders a comprehensive security assessment. Additionally, medium-severity prompt injection risks are present, potentially enabling unauthorized command execution or data manipulation.
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 37; the rest are in the per-scanner reports above.