Add your description here
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.
3 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 -- simplify-html-for-llm
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
3 findings · 6.8s
v0.3.74
0 findings · 1.8s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
v0.71.0
70 findings · 0.3s
v2.3.8
70 findings · 1.5s
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 · 1.7s
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 | Flagged49 | — | 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 143 findings across every scanner that examined this package. None of the 3 findings rated critical by their scanner were dismissed.
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-2f96-g7mh-g2hx
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-3f7w-8rr8-f37f
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-3rp5-jjmw-4wv2
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-4gmw-gg2m-w46p
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-539m-9xh6-q6rr
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-6p8h-3wgx-97gf
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-94p4-4cq8-9g67
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-956x-8gvw-wg5v
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-9rj7-rf2p-w77r
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-fjr4-x663-mwxc
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-hh9p-6wh2-4mfc
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-hmq2-w58f-27jc
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-jm78-9fvv-mhgr
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-mv93-w799-cj2w
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-p538-c434-8v24
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-pw6j-qg29-8w7f
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-r9mr-m37c-5fr3
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-rwj8-pgh3-r573
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
2 GHSA-wvpp-8hx9-p66j
Files: uv.lock, /repo/uv.lock · reported by trivy, osv-scanner
1 CVE-2024-47081
Files: uv.lock · reported by trivy
1 CVE-2025-43859
Files: uv.lock · reported by trivy
1 CVE-2025-4565
Files: uv.lock · reported by trivy
1 CVE-2025-47287
Files: uv.lock · reported by trivy
1 CVE-2025-48379
Files: uv.lock · reported by trivy
1 CVE-2025-50181
Files: uv.lock · reported by trivy
1 CVE-2025-50182
Files: uv.lock · reported by trivy
1 CVE-2025-66418
Files: uv.lock · reported by trivy
1 CVE-2025-66471
Files: uv.lock · reported by trivy
1 CVE-2025-67724
Files: uv.lock · reported by trivy
1 CVE-2025-67725
Files: uv.lock · reported by trivy
1 CVE-2025-67726
Files: uv.lock · reported by trivy
1 CVE-2025-71176
Files: uv.lock · reported by trivy
1 CVE-2026-0994
Files: uv.lock · reported by trivy
1 CVE-2026-10804
Files: uv.lock · reported by trivy
1 CVE-2026-21441
Files: uv.lock · reported by trivy
1 CVE-2026-25087
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-25990
Files: uv.lock · reported by trivy
1 CVE-2026-31958
Files: uv.lock · reported by trivy
1 CVE-2026-33682
Files: uv.lock · reported by trivy
1 CVE-2026-35536
Files: uv.lock · reported by trivy
1 CVE-2026-40192
Files: uv.lock · reported by trivy
1 CVE-2026-42215
Files: uv.lock · reported by trivy
1 CVE-2026-42284
Files: uv.lock · reported by trivy
1 CVE-2026-42308
Files: uv.lock · reported by trivy
1 CVE-2026-42309
Files: uv.lock · reported by trivy
1 CVE-2026-42310
Files: uv.lock · reported by trivy
1 CVE-2026-42311
Files: uv.lock · reported by trivy
1 CVE-2026-44243
Files: uv.lock · reported by trivy
1 CVE-2026-44244
Files: uv.lock · reported by trivy
1 CVE-2026-44431
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-49476
Files: uv.lock · reported by trivy
1 CVE-2026-49477
Files: uv.lock · reported by trivy
1 CVE-2026-49853
Files: uv.lock · reported by trivy
1 CVE-2026-49854
Files: uv.lock · reported by trivy
1 CVE-2026-49855
Files: uv.lock · reported by trivy
1 CVE-2026-54058
Files: uv.lock · reported by trivy
1 CVE-2026-54059
Files: uv.lock · reported by trivy
1 CVE-2026-54060
Files: uv.lock · reported by trivy
1 CVE-2026-55379
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-55798
Files: uv.lock · reported by trivy
1 CVE-2026-59197
Files: uv.lock · reported by trivy
1 CVE-2026-59198
Files: uv.lock · reported by trivy
1 CVE-2026-59199
Files: uv.lock · reported by trivy
1 CVE-2026-59200
Files: uv.lock · reported by trivy
1 CVE-2026-59204
Files: uv.lock · reported by trivy
1 CVE-2026-59205
Files: uv.lock · reported by trivy
1 GHSA-78cv-mqj4-43f7
Files: uv.lock · reported by trivy
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2025-265
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-266
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-267
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2025-61
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-113
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-140
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1805
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1806
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1974
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1994
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1997
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1998
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1999
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-212
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2160
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2162
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2163
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2250
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2251
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2252
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2285
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2287
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3071
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3072
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3387
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3388
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3389
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-348
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner
Critical vulnerabilities found in installed dependencies
The artifact includes multiple critical and high severity vulnerabilities within its installed dependencies, as identified in the `uv.lock` file. These vulnerabilities could potentially enable remote code execution, information disclosure, or denial of service. Attention is warranted for the three critical findings (PYSEC-2026-2161, CVE-2025-43859, PYSEC-2026-348) and numerous high severity issues.
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 101; the rest are in the per-scanner reports above.