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.
10 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 -- project-timeline-vis
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.6s
v0.3.74
1 finding · 2.1s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
v0.71.0
36 findings · 0.2s
v2.3.8
138 findings · 7.0s
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 22, 2026 | Flagged47 | — | 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 180 findings across every scanner that examined this package. None of the 10 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.
4 CVE-2026-44288
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
4 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-968p-4wvh-cqc8
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-f886-m6hf-6m8v
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-q6x5-8v7m-xcrf
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
4 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 CVE-2025-27789
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-33532
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-41242
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-44289
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-44290
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-44291
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-44292
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-44293
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-44294
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-45740
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-48068
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-48069
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-48712
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-54269
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-54466
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 CVE-2026-54490
Files: pnpm-lock.yaml, yarn.lock · reported by trivy
2 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-28wg-ghj8-5hjv
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-2pr8-phx7-x9h3
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-356w-63v5-8wf4
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-3v7f-55p6-f55p
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-48c2-rrv3-qjmp
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-4r4m-qw57-chr8
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-4w7w-66w2-5vf9
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-4x5r-pxfx-6jf8
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-5375-pq7m-f5r2
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-66ff-xgx4-vchm
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-67mh-4wv8-2f99
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-685m-2w69-288q
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-6g55-p6wh-862q
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-75px-5xx7-5xc7
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-859w-5945-r5v3
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-93m4-6634-74q7
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-99f4-grh7-6pcq
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-f38q-mgvj-vph7
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-fx83-v9x8-x52w
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-g4jq-h2w9-997c
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-jggg-4jg4-v7c6
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-jqfw-vq24-v9c3
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-jvwf-75h9-cwgg
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-mp7j-qc5w-4988
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-mw96-cpmx-2vgc
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-p9ff-h696-f583
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-rf6f-7fwh-wjgh
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-v56q-mh7h-f735
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-v6wh-96g9-6wx3
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-wcpc-wj8m-hjx6
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-wf6x-7x77-mvgw
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-x574-m823-4x7w
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xcj6-pq6g-qj4x
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xffm-g5w8-qvg7
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xq3m-2v4x-88gg
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xv26-6w52-cph6
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
2 GHSA-xvcm-6775-5m9r
Files: /repo/pnpm-lock.yaml, /repo/yarn.lock · reported by osv-scanner
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 HIDDEN_DATA_FILE
Files: /repo/.firebaserc · reported by cisco-skill-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 YARA_prompt_injection_unicode_steganography
Files: /repo/public/megpt.png · reported by cisco-skill-scanner
Critical vulnerabilities found in artifact dependencies.
This artifact contains critical vulnerabilities in its dependencies, identified in both pnpm-lock.yaml and yarn.lock files. These issues could lead to various security exposures, including potential remote code execution or data compromise. Additionally, the overall analyzability of the artifact's code is low, which may hinder further security assessment.
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 91; the rest are in the per-scanner reports above.