Loading the registry…
A CLI tool to install different cursor rules for various project types
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 -- cursor-rules-cli
7 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.
v1.4.0
0 findings · 1.0s
v2.0.11
10 findings · 9.4s
v0.3.74
0 findings · 1.5s
v0.1.0
0 findings · 4.7s
v0.1.0
0 findings · 4.7s
v0.71.0
0 findings · 0.3s
v2.3.8
22 findings · 10.6s
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 · 2.2s
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 | Flagged72 | — | agentshield: completecisco-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 32 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 5 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
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.
4 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: LOW_ANALYZABILITY, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_INVALID_NAME and 1 more · Files: /repo/src/__tests__, /repo/src/__tests__/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2qvq-rjwj-gvw9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2w6w-674q-4c4q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3mfm-83xf-c92r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-442j-39wm-28r2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7rx3-28cr-v5wh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9cx6-37pm-9jff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xhpv-hc6g-r9c6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xjpj-3mr7-gcpf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
5 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_FS_ACCESS, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/src/templates.ts, /repo/SKILL.md, /repo/.cursor/commands/SKILL.md · reported by cisco-skill-scanner
Critical vulnerability and potential data egress identified.
A critical vulnerability exists in a dependency, identified in `pnpm-lock.yaml`. The artifact also exhibits file system access capabilities in `src/templates.ts`, which could lead to data egress. Additionally, multiple high-severity dependency vulnerabilities are present, and some code is difficult to analyze.
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.