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.
1 critical finding 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 -- namly-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.1s
v2.0.11
7 findings · 21.3s
v0.3.74
0 findings · 8.5s
v0.1.0
0 findings · 6.6s
v0.1.0
0 findings · 6.6s
v0.71.0
29 findings · 0.7s
v2.3.8
49 findings · 10.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.1s
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 | Flagged46 | — | 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 85 findings across every scanner that examined this package. None of the 1 finding 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.
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-rgw5-rvv9-x895
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-frvp-7c67-39w9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-h67p-54hq-rp68
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
2 LOW_ANALYZABILITY
Files: /repo/scripts, /repo · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/scripts/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/scripts/SKILL.md · reported by cisco-skill-scanner
1 CVE-2026-12590
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-39406
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47673
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47674
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47675
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-47676
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-54286
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54287
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54288
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54289
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54290
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59895
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59896
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59897
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-59952
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69207
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71848
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71849
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71850
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-23hp-3jrh-7fpw
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2gcr-mfcq-wcc3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3hrh-pfw6-9m5x
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-54fx-42gc-7vw4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5qjj-4xww-7phc
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-79qm-7rj5-m7r9
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-88fw-hqm2-52qc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
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-92pp-h63x-v22m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f577-qrjj-4474
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-hmw2-7cc7-3qxx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hvrm-45r6-mjfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
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-r292-9mhp-454m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
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-v422-hmwv-36x6
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-w62v-xxxg-mg59
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-w8wr-v893-vjvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xrhx-7g5j-rcj5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
Critical and high-severity vulnerabilities detected in dependencies
The artifact contains a critical vulnerability (GHSA-23hp-3jrh-7fpw) and multiple high-severity vulnerabilities in its dependencies, primarily identified in `pnpm-lock.yaml`. These issues could lead to various impacts depending on the specific vulnerability, such as remote code execution, denial of service, or information disclosure. Additionally, the artifact's overall analyzability is low, as indicated by findings in `/repo` and `/repo/scripts`, which may hinder further security assessment. Reviewing the identified vulnerabilities and their potential impact on the artifact's functionality is recommended.
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 30; the rest are in the per-scanner reports above.