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.
1 critical finding reported by 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 -- craigmdennis/home-assistant-newspaper-frontpage
5 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.
v0.3.74
0 findings · 0.7s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
37 findings · 0.2s
v2.3.8
37 findings · 1.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
v2.0.11
No skill bundle was found in this artifact. What each scanner covers
0 findings · 7.0s
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 | Flagged50 | — | agentshield ·n/a: not applicablecisco-skill-scanner ·n/a: not applicableagent-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 74 findings across every scanner that examined this package. None of the 1 finding 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.
1 CVE-2024-27306
Files: requirements.txt · reported by trivy
1 CVE-2024-30251
Files: requirements.txt · reported by trivy
1 CVE-2024-52304
Files: requirements.txt · reported by trivy
1 CVE-2025-53643
Files: requirements.txt · reported by trivy
1 CVE-2025-69223
Files: requirements.txt · reported by trivy
1 CVE-2025-69224
Files: requirements.txt · reported by trivy
1 CVE-2025-69225
Files: requirements.txt · reported by trivy
1 CVE-2025-69226
Files: requirements.txt · reported by trivy
1 CVE-2025-69227
Files: requirements.txt · reported by trivy
1 CVE-2025-69228
Files: requirements.txt · reported by trivy
1 CVE-2025-69229
Files: requirements.txt · reported by trivy
1 CVE-2025-69230
Files: requirements.txt · reported by trivy
1 CVE-2026-22815
Files: requirements.txt · reported by trivy
1 CVE-2026-28684
Files: requirements.txt · reported by trivy
1 CVE-2026-34513
Files: requirements.txt · reported by trivy
1 CVE-2026-34514
Files: requirements.txt · reported by trivy
1 CVE-2026-34515
Files: requirements.txt · reported by trivy
1 CVE-2026-34516
Files: requirements.txt · reported by trivy
1 CVE-2026-34517
Files: requirements.txt · reported by trivy
1 CVE-2026-34518
Files: requirements.txt · reported by trivy
1 CVE-2026-34519
Files: requirements.txt · reported by trivy
1 CVE-2026-34520
Files: requirements.txt · reported by trivy
1 CVE-2026-34525
Files: requirements.txt · reported by trivy
1 CVE-2026-34993
Files: requirements.txt · reported by trivy
1 CVE-2026-47265
Files: requirements.txt · reported by trivy
1 CVE-2026-50269
Files: requirements.txt · reported by trivy
1 CVE-2026-54273
Files: requirements.txt · reported by trivy
1 CVE-2026-54274
Files: requirements.txt · reported by trivy
1 CVE-2026-54275
Files: requirements.txt · reported by trivy
1 CVE-2026-54276
Files: requirements.txt · reported by trivy
1 CVE-2026-54277
Files: requirements.txt · reported by trivy
1 CVE-2026-54278
Files: requirements.txt · reported by trivy
1 CVE-2026-54279
Files: requirements.txt · reported by trivy
1 CVE-2026-54280
Files: requirements.txt · reported by trivy
1 CVE-2026-59881
Files: requirements.txt · reported by trivy
1 CVE-2026-69243
Files: requirements.txt · reported by trivy
1 CVE-2026-69244
Files: requirements.txt · reported by trivy
1 PYSEC-2026-1097
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1098
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1099
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1100
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1102
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1103
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1104
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1105
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1106
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1109
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/requirements.txt · reported by osv-scanner
Artifact uses dependencies with critical and high-severity vulnerabilities.
The artifact's installed code includes dependencies with a critical vulnerability (PYSEC-2026-2102) and numerous high-severity vulnerabilities. These issues, identified in the requirements.txt file, could lead to various impacts depending on the specific vulnerability. Reviewing these dependencies is essential before deployment.
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.