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 -- polyvibe-website
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.6s
v2.0.11
7 findings · 8.6s
v0.3.74
2 findings · 5.0s
v0.1.0
0 findings · 3.6s
v0.1.0
0 findings · 3.6s
v0.71.0
31 findings · 0.3s
v2.3.8
106 findings · 7.7s
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.0s
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 19, 2026 | Flagged46 | — | 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 146 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 30 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.
3 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/package-lock.json · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-5j98-mcp5-4vw2
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-6475-r3vj-m8vf
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-6rw7-vpxm-498p
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-8gc5-j5rx-235r
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-fj3w-jwp8-x2g3
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-gh4j-gqv2-49f6
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-jmr7-xgp7-cmfj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-jp2q-39xq-3w4g
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-m7jm-9gc2-mpf2
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mwv6-3258-q52c
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-w7fw-mjwx-w883
Files: /repo/package-lock.json · reported by osv-scanner
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-2025-59471
Files: package-lock.json · reported by trivy
1 CVE-2026-27980
Files: package-lock.json · reported by trivy
1 CVE-2026-29057
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-44572
Files: package-lock.json · reported by trivy
1 CVE-2026-44576
Files: package-lock.json · reported by trivy
1 CVE-2026-44577
Files: package-lock.json · reported by trivy
1 CVE-2026-44580
Files: package-lock.json · reported by trivy
1 CVE-2026-44581
Files: package-lock.json · reported by trivy
1 CVE-2026-44582
Files: package-lock.json · reported by trivy
1 CVE-2026-59952
Files: package-lock.json · reported by trivy
1 CVE-2026-64643
Files: package-lock.json · reported by trivy
1 CVE-2026-64645
Files: package-lock.json · reported by trivy
1 CVE-2026-64646
Files: package-lock.json · reported by trivy
1 CVE-2026-64647
Files: package-lock.json · reported by trivy
1 CVE-2026-64648
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 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2mjp-6q6p-2qxm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35p6-xmwp-9g52
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-36p8-mvp6-cv38
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-48c2-rrv3-qjmp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4992-7rv2-5pvq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-58qx-3vcg-4xpx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5j59-xgg2-r9c4
Files: package-lock.json · reported by trivy
1 GHSA-5qjj-4xww-7phc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-737v-mqg7-c878
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7h2j-956f-4vf2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9g9p-9gw9-jx7f
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-ffhc-5mcf-pf4q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g8m3-5g58-fq7m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g9mf-h72j-4rw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h25m-26qc-wcjf
Files: package-lock.json · reported by trivy
1 GHSA-h64f-5h5j-jqjh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j3q9-mxjg-w52f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jr45-8vmc-qm54
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
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-p88m-4jfj-68fv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pr7r-676h-xcf6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v9p9-hfj2-hcw8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vfv6-92ff-j949
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vqpr-j7v3-hqw9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vrm6-8vpv-qv8q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vxpw-j846-p89q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xcpc-8h2w-3j85
Files: /repo/package-lock.json · reported by osv-scanner
25 The review call did not complete.
Rules: LOW_ANALYZABILITY, CVE-2026-45623, GHSA-2v37-7h3g-55p8 and 21 more · Files: /repo/.cursor/commands, package-lock.json, /repo/package-lock.json and 1 more · reported by cisco-skill-scanner, trivy, osv-scanner
5 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, OVERSIZED_FILE, MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md, /repo/.cursor/commands/SKILL.md, /repo/public/videos/vibe-coding.mp4 · reported by cisco-skill-scanner
Critical vulnerabilities found in dependencies.
The artifact includes a critical vulnerability in its dependencies, identified in `package-lock.json`, which could lead to arbitrary code execution or sensitive data exposure. Numerous high-severity vulnerabilities are also present in dependencies, posing additional risks. Furthermore, sections of the artifact, specifically `/repo` and `/repo/.cursor/commands`, show low analyzability, which may conceal other security 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 25; the rest are in the per-scanner reports above.