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.
13 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 -- desbrava
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
29 findings · 14.3s
v0.3.74
3 findings · 5.7s
v0.1.0
1 finding · 4.5s
v0.1.0
0 findings · 4.6s
v0.71.0
61 findings · 1.1s
v2.3.8
102 findings · 9.8s
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 20, 2026 | Flagged34 | — | 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 196 findings across every scanner that examined this package. None of the 13 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 19 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.
8 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/components/SKILL.md, /repo/docs/usages/SKILL.md, /repo/docs/hooks/SKILL.md and 1 more · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 CVE-2026-44288
Files: package-lock.json · reported by trivy
2 CVE-2026-73418
Files: package-lock.json · reported by trivy
2 CVE-2026-73419
Files: package-lock.json · reported by trivy
2 CVE-2026-73420
Files: package-lock.json · reported by trivy
2 GHSA-23c5-xmqv-rm74
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-3ppc-4f35-3m26
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-5jpx-9hw9-2fx4
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-6g55-p6wh-862q
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-7r86-cg39-jmmj
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-7rqj-j65f-68wh
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-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-f88m-g3jw-g9cj
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-h25m-26qc-wcjf
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-mh99-v99m-4gvg
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-q6x5-8v7m-xcrf
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-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-w37m-7fhw-fmv9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-x445-f3h2-j279
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-xmf8-cvqr-rfgj
Files: /repo/package-lock.json · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SECRET-004
Files: lib/services/places/base.ts · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2025-55182
Files: package-lock.json · reported by trivy
1 CVE-2025-57822
Files: package-lock.json · reported by trivy
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-41242
Files: package-lock.json · reported by trivy
1 CVE-2026-41305
Files: package-lock.json · reported by trivy
1 CVE-2026-44289
Files: package-lock.json · reported by trivy
1 CVE-2026-44290
Files: package-lock.json · reported by trivy
1 CVE-2026-44291
Files: package-lock.json · reported by trivy
1 CVE-2026-44292
Files: package-lock.json · reported by trivy
1 CVE-2026-44293
Files: package-lock.json · reported by trivy
1 CVE-2026-44294
Files: package-lock.json · reported by trivy
1 CVE-2026-44572
Files: package-lock.json · reported by trivy
1 CVE-2026-44573
Files: package-lock.json · reported by trivy
1 CVE-2026-44574
Files: package-lock.json · reported by trivy
1 CVE-2026-44575
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-44578
Files: package-lock.json · reported by trivy
1 CVE-2026-44579
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-45109
Files: package-lock.json · reported by trivy
1 CVE-2026-45623
Files: package-lock.json · reported by trivy
1 CVE-2026-45740
Files: package-lock.json · reported by trivy
1 CVE-2026-48068
Files: package-lock.json · reported by trivy
1 CVE-2026-48069
Files: package-lock.json · reported by trivy
1 CVE-2026-48712
Files: package-lock.json · reported by trivy
1 CVE-2026-54269
Files: package-lock.json · reported by trivy
1 CVE-2026-54466
Files: package-lock.json · reported by trivy
1 CVE-2026-54490
Files: package-lock.json · reported by trivy
1 CVE-2026-59877
Files: package-lock.json · reported by trivy
1 CVE-2026-64641
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-64649
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-73421
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-23hp-3jrh-7fpw
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-267c-6grr-h53f
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-26hh-7cqf-hhc6
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-2pr8-phx7-x9h3
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-34x7-hfp2-rc4v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
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-4342-x723-ch2f
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-492v-c6pp-mqqv
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-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5375-pq7m-f5r2
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-66ff-xgx4-vchm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-685m-2w69-288q
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-75px-5xx7-5xc7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-83g3-92jg-28cx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8fpg-xm3f-6cx3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8qq5-rm4j-mr97
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8x88-c5mf-7j5w
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-99f4-grh7-6pcq
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-9ppj-qmqm-q256
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9qr9-h5gf-34mp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-c4j6-fc7j-m34r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f38q-mgvj-vph7
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-fx83-v9x8-x52w
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-gvwx-54wh-qm9j
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-h64f-5h5j-jqjh
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-j3f2-48v5-ccww
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jggg-4jg4-v7c6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-jvwf-75h9-cwgg
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-mg66-mrh9-m8jx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mp7j-qc5w-4988
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-qffp-2rhf-9h96
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r292-9mhp-454m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r6q2-hw4h-h46w
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-vfv6-92ff-j949
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vmf3-w455-68vh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wcpc-wj8m-hjx6
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-xq3m-2v4x-88gg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xv26-6w52-cph6
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/lib/services/places/base.ts · reported by nerlo-behavioral
19 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: DATA_EXFIL_JS_NETWORK, HIDDEN_DATA_FILE, SOCIAL_ENG_VAGUE_DESCRIPTION and 1 more · Files: /repo/hooks/useActivities.ts, /repo/hooks/useTrips.ts, /repo/lib/services/places/base.ts and 3 more · reported by cisco-skill-scanner
Critical vulnerabilities and credential risks identified
This artifact contains multiple critical vulnerabilities, primarily within its dependencies as listed in `package-lock.json`. A high-severity finding in `lib/services/places/base.ts` indicates potential for credential access and network egress. These issues require immediate review due to their severe impact.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 25; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.