Loading the registry…
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.
2 critical findings 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 -- chi
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
5 findings · 7.0s
v0.3.74
5 findings · 1.5s
v0.1.0
0 findings · 2.9s
v0.1.0
0 findings · 2.9s
v0.71.0
60 findings · 0.3s
v2.3.8
61 findings · 1.3s
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 21, 2026 | Flagged47 | — | 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 131 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
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.
5 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/docker-publish.yml · reported by agent-audit-kit
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 FILE_MAGIC_MISMATCH
Files: /repo/knowledge/example.zeus_sn18.yaml, /repo/knowledge/sdk.quick_reference.yaml · reported by cisco-skill-scanner
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
The model could have called any of these a false positive and did not.
1 CVE-2026-54282
Files: uv.lock · reported by trivy
Critical vulnerabilities found in dependencies and potential resource abuse.
The artifact includes dependencies with critical vulnerabilities (PYSEC-2026-2102, PYSEC-2026-2161) identified in `/repo/uv.lock`. Additionally, a high-severity finding indicates a potential for resource abuse through an infinite loop in `/repo/validator.py`. Multiple other high-severity vulnerabilities are present in various dependencies.
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.
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-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-2025-47273
Files: uv.lock · reported by trivy
1 CVE-2026-22815
Files: uv.lock · reported by trivy
1 CVE-2026-24049
Files: uv.lock · reported by trivy
1 CVE-2026-25645
Files: uv.lock · reported by trivy
1 CVE-2026-34513
Files: uv.lock · reported by trivy
1 CVE-2026-34514
Files: uv.lock · reported by trivy
1 CVE-2026-34515
Files: uv.lock · reported by trivy
1 CVE-2026-34516
Files: uv.lock · reported by trivy
1 CVE-2026-34517
Files: uv.lock · reported by trivy
1 CVE-2026-34518
Files: uv.lock · reported by trivy
1 CVE-2026-34519
Files: uv.lock · reported by trivy
1 CVE-2026-34520
Files: uv.lock · reported by trivy
1 CVE-2026-34525
Files: uv.lock · reported by trivy
1 CVE-2026-34993
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-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-44432
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-47265
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-50269
Files: uv.lock · reported by trivy
1 CVE-2026-54273
Files: uv.lock · reported by trivy
1 CVE-2026-54274
Files: uv.lock · reported by trivy
1 CVE-2026-54275
Files: uv.lock · reported by trivy
1 CVE-2026-54276
Files: uv.lock · reported by trivy
1 CVE-2026-54277
Files: uv.lock · reported by trivy
1 CVE-2026-54278
Files: uv.lock · reported by trivy
1 CVE-2026-54279
Files: uv.lock · reported by trivy
1 CVE-2026-54280
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-59881
Files: uv.lock · reported by trivy
1 CVE-2026-59890
Files: uv.lock · reported by trivy
1 CVE-2026-69243
Files: uv.lock · reported by trivy
1 CVE-2026-69244
Files: uv.lock · reported by trivy
1 GHSA-6v7p-g79w-8964
Files: uv.lock · reported by trivy
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2025-49
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-142
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2047
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2094
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2095
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2096
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2097
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2099
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2100
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2101
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2103
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2107
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2108
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2109
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2110
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2113
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-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3447
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3625
Files: /repo/uv.lock · reported by osv-scanner
1 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/validator.py · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
Showing 25 of 70; the rest are in the per-scanner reports above.