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.
2 critical findings reported by trivy, 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 -- echonote
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
5 findings · 6.5s
v0.3.74
1 finding · 0.9s
v0.1.0
0 findings · 2.9s
v0.1.0
0 findings · 2.9s
v0.71.0
28 findings · 0.2s
v2.3.8
52 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.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 | Flagged49 | — | 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 86 findings across every scanner that examined this package. None of the 2 findings 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.
2 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-r292-9mhp-454m
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/.cursor/rules/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/.cursor/rules/SKILL.md · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 CVE-2025-58751
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-58752
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-62522
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23745
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-23950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-24842
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-26960
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27606
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29786
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31802
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33671
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-33672
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39363
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39365
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45623
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53571
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53632
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53655
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59871
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59873
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59874
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59875
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-73646
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-23hp-3jrh-7fpw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-34x7-hfp2-rc4v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
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-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-83g3-92jg-28cx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-93m4-6634-74q7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9ppj-qmqm-q256
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gvwx-54wh-qm9j
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-jqfw-vq24-v9c3
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-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9ff-h696-f583
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qffp-2rhf-9h96
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
Critical vulnerabilities found in installed dependencies
This artifact contains critical and high severity vulnerabilities within its installed dependencies, as identified in `pnpm-lock.yaml`. These vulnerabilities could enable various impacts, including remote code execution, denial of service, or information disclosure. Multiple critical and high severity findings warrant immediate attention to mitigate potential risks.
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 49; the rest are in the per-scanner reports above.