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 -- oneproperty
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 · 0.5s
v2.0.11
4 findings · 6.6s
v0.3.74
2 findings · 1.7s
v0.1.0
0 findings · 3.0s
v0.1.0
0 findings · 3.0s
v0.71.0
27 findings · 0.2s
v2.3.8
40 findings · 6.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 · 1.8s
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 | Flagged48 | — | 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 73 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 2 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.
2 GHSA-qwww-vcr4-c8h2
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2026-27606
Files: package-lock.json · reported by trivy
1 CVE-2026-33244
Files: package-lock.json · reported by trivy
1 CVE-2026-33245
Files: package-lock.json · reported by trivy
1 CVE-2026-33671
Files: package-lock.json · reported by trivy
1 CVE-2026-33672
Files: package-lock.json · reported by trivy
1 CVE-2026-34077
Files: package-lock.json · reported by trivy
1 CVE-2026-39363
Files: package-lock.json · reported by trivy
1 CVE-2026-39364
Files: package-lock.json · reported by trivy
1 CVE-2026-39365
Files: package-lock.json · reported by trivy
1 CVE-2026-40181
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-42211
Files: package-lock.json · reported by trivy
1 CVE-2026-42342
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-53571
Files: package-lock.json · reported by trivy
1 CVE-2026-53632
Files: package-lock.json · reported by trivy
1 CVE-2026-53663
Files: package-lock.json · reported by trivy
1 CVE-2026-53666
Files: package-lock.json · reported by trivy
1 CVE-2026-53667
Files: package-lock.json · reported by trivy
1 CVE-2026-53668
Files: package-lock.json · reported by trivy
1 CVE-2026-53669
Files: package-lock.json · reported by trivy
1 CVE-2026-55685
Files: package-lock.json · reported by trivy
1 CVE-2026-67213
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
Files: package-lock.json · reported by trivy
1 CVE-2026-69153
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 FILE_MAGIC_MISMATCH
Files: /repo/vite.config.js · reported by cisco-skill-scanner
1 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-25h7-pfq9-p65f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2j2x-hqr9-3h42
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-337j-9hxr-rhxg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-49rj-9fvp-4h2h
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-84g9-w2xq-vcv6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8646-j5j9-6r62
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8x6r-g9mw-2r78
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-chx6-hx7r-mcp5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f22v-gfqf-p8f3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h8fp-f39c-q6mh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jjmj-jmhj-qwj2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mw96-cpmx-2vgc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rxv8-25v2-qmq8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v2wj-q39q-566r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wrjc-x8rr-h8h6
Files: /repo/package-lock.json · reported by osv-scanner
1 YARA_prompt_injection_unicode_steganography
Files: /repo/src/assets/heroImages/plumbing.png · reported by cisco-skill-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Critical vulnerabilities found in dependencies.
The artifact contains 40 distinct high-severity vulnerabilities in its installed dependencies, primarily identified in `/repo/package-lock.json`. These findings from `osv-scanner` and `trivy` indicate significant security risks. Reviewing the specific GHSA and CVE identifiers, such as GHSA-49rj-9fvp-4h2h and CVE-2026-73646, is essential to understand potential impacts like remote code execution or data compromise.
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 40; the rest are in the per-scanner reports above.