Loading the registry…
<p align="center"> <a href="http://nestjs.com/" target="blank"><img src="https://nestjs.com/img/logo-small.svg" width="120" alt="Nest Logo" /></a> </p>
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 -- backend
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 · 1.0s
v2.0.11
3 findings · 8.8s
v0.3.74
0 findings · 2.4s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 4.3s
v0.71.0
23 findings · 0.3s
v2.3.8
81 findings · 9.1s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
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 22, 2026 | Flagged48 | — | 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 107 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.
4 GHSA-23c5-xmqv-rm74
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-3ppc-4f35-3m26
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
4 GHSA-7r86-cg39-jmmj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-2g4f-4pwh-qvx6
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-3v7f-55p6-f55p
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-5p4m-2wfm-xmqj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-5v7r-6r5c-r473
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-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-mh29-5h37-fv8m
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-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-v6h2-p8h4-qcjw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 CVE-2025-12758
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-13465
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-13466
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-15284
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-48997
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-56200
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-7338
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2359
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2391
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-2950
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-31808
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-32630
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-3304
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-3520
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-35515
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41907
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4800
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4923
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-4926
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-8723
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-27v5-c462-wpq7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-36xv-jgw5-4q75
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-38r7-794h-5758
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-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-52f5-9888-hmc6
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5528-5vmv-3xc2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5c6j-r48x-rmvq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5j98-mcp5-4vw2
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6rw7-vpxm-498p
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-73rr-hh4g-fpgx
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-8fgc-7cc6-rx7x
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9965-vmph-33xx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23m-r3pf-42rh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fjgf-rc76-4x9p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fjxv-7rqg-78g4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g5hg-p3ph-g8qg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gmq8-994r-jv83
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-j3q9-mxjg-w52f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j47w-4g3g-c36v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mp2f-45pm-3cg9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ph9p-34f9-6g65
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-qj8w-gfj5-8c6v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-r5fr-rjxr-66jc
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-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-v52c-386h-88mc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vghf-hv5q-vc2g
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w5hq-g745-h8pq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w7fw-mjwx-w883
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wqch-xfxh-vrr4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-x9g3-xrwr-cwfg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xf7r-hgr6-v32p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xffm-g5w8-qvg7
Files: /repo/pnpm-lock.yaml · reported by osv-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
Critical vulnerabilities identified in artifact dependencies
This artifact contains critical vulnerabilities in its dependencies, specifically GHSA-fjxv-7rqg-78g4 and GHSA-mp2f-45pm-3cg9. Numerous high severity vulnerabilities are also present, many of which are identified within the pnpm-lock.yaml file. These findings indicate potential risks related to the integrity and security of the installed code.
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 58; the rest are in the per-scanner reports above.