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 -- zeno
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
21 findings · 8.1s
v0.3.74
3 findings · 3.5s
v0.1.0
5 findings · 4.5s
v0.1.0
0 findings · 4.5s
v0.71.0
95 findings · 0.3s
v2.3.8
114 findings · 7.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 · 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 21, 2026 | Flagged36 | — | 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 238 findings across every scanner that examined this package.
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.
11 MANIFEST_MISSING_LICENSE
Files: /repo/.cursor/skills/zeno-memory-service/SKILL.md, /repo/.cursor/skills/zeno-intent-routing/SKILL.md, /repo/.cursor/skills/zeno-environment-config/SKILL.md and 8 more · reported by cisco-skill-scanner
4 DATA_EXFIL_JS_NETWORK
Files: /repo/src/modules/agent/intent/intent-transformer.service.ts, /repo/src/modules/ai/ai.service.ts, /repo/src/modules/lark/slides/lark-slides.service.ts · reported by cisco-skill-scanner
4 GHSA-42h9-826w-cgv3
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
4 GHSA-7q8q-rj6j-mhjq
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
4 GHSA-jqh4-m9w3-8hp9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
4 GHSA-mmx7-hfxf-jppx
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
4 GHSA-mwf2-3pr3-8698
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
4 GHSA-pmv8-rq9r-6j72
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
4 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/modules/agent/intent/intent-transformer.service.ts, /repo/src/modules/ai/ai.service.ts, /repo/src/modules/lark/slides/lark-slides.service.ts · reported by nerlo-behavioral
3 CVE-2026-41907
Files: pnpm-lock.yaml · reported by trivy
3 CVE-2026-44288
Files: pnpm-lock.yaml · reported by trivy
3 CVE-2026-44902
Files: pnpm-lock.yaml · reported by trivy
3 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
3 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-q6x5-8v7m-xcrf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-q7rr-3cgh-j5r3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-w5hq-g745-h8pq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/.cursor/plans/SKILL.md, /repo/.cursor/commands/SKILL.md · reported by cisco-skill-scanner
2 AAK-SECRET-004
Files: src/modules/lark/lark.service.ts, src/modules/ai/ai.service.ts · reported by agent-audit-kit
2 CVE-2026-44289
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44290
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44291
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44292
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44293
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44294
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44486
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44487
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44488
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44490
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44494
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-44496
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-45736
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-45740
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-48712
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-48779
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-54269
Files: pnpm-lock.yaml · reported by trivy
2 CVE-2026-59877
Files: pnpm-lock.yaml · reported by trivy
2 GHSA-2pr8-phx7-x9h3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-35jp-ww65-95wh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-58qx-3vcg-4xpx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-66ff-xgx4-vchm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-685m-2w69-288q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-75px-5xx7-5xc7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-777c-7fjr-54vf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-898c-q2cr-xwhg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-96hv-2xvq-fx4p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f38q-mgvj-vph7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-f4gw-2p7v-4548
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-fx83-v9x8-x52w
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-g7r4-m6w7-qqqr
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-gcfj-64vw-6mp9
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-hcpx-6fm6-wx23
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-hfxv-24rg-xrqf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j3f2-48v5-ccww
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-j5f8-grm9-p9fc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-jggg-4jg4-v7c6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-jvwf-75h9-cwgg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-p92q-9vqr-4j8v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-wcpc-wj8m-hjx6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 AAK-SUPPLY-003
Files: package.json · reported by agent-audit-kit
1 CVE-2025-62718
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12143
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-40175
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42033
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42034
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42035
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42036
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42037
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42038
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42039
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42040
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42041
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42042
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42043
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42044
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-42264
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44489
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44492
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44495
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-45134
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48068
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-48069
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-5038
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-5079
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-53550
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54285
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59725
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59892
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67314
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69185
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-8723
Files: pnpm-lock.yaml · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-2m8v-j782-fhvr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3644-q5cj-c5c7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3g43-6gmg-66jw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3p4h-7m6x-2hcm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-445q-vr5w-6q77
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-45rx-2jwx-cxfr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c8g-83qw-93j6
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-5375-pq7m-f5r2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5c9x-8gcm-mpgx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-62hf-57xw-28j9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-654m-c8p4-x5fp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-72gw-mp4g-v24j
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8988-4f7v-96qf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-99f4-grh7-6pcq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-jxxr-4gwj-5jf2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m7pr-hjqh-92cm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pf86-5x62-jrwf
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pjwm-pj3p-43mv
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q3j6-qgpj-74h6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8qp-cvcw-x6jj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r635-g3xr-vw7x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v39h-62p7-jpjc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w9j2-pvgh-6h63
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xj6q-8x83-jv6g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/.cursor/plans/SKILL.md · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-hardcoded-external-egress
Files: /repo/src/modules/lark/slides/lark-slides.service.ts · reported by nerlo-behavioral
High-severity vulnerabilities and secret exposure detected
The artifact contains multiple high-severity vulnerabilities in its dependencies, which could lead to various security risks. Additionally, secrets are exposed in `src/modules/ai/ai.service.ts` and `src/modules/lark/lark.service.ts`, and these secrets are used for network egress in `src/modules/agent/intent/intent-transformer.service.ts`, `src/modules/ai/ai.service.ts`, and `src/modules/lark/slides/lark-slides.service.ts`. These findings indicate potential for unauthorized access or data exfiltration.
Concern level assessed by the review: High. 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 111; the rest are in the per-scanner reports above.