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.
2 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 -- zonepal
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
8 findings · 6.8s
v0.3.74
2 findings · 2.0s
v0.1.0
1 finding · 2.9s
v0.1.0
0 findings · 2.9s
v0.71.0
38 findings · 0.2s
v2.3.8
58 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 20, 2026 | Flagged41 | — | 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.
Not reviewed is not the same as clean. Those 51 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.
2 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/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
2 AAK-LEGAL-002
Files: package.json, apps/web-app/package.json · reported by agent-audit-kit
2 DATA_EXFIL_JS_NETWORK
Files: /repo/apps/web-app/src/app/api/weather/route.ts, /repo/apps/web-app/src/components/weather-icon.tsx · reported by cisco-skill-scanner
2 GHSA-55q2-fjhq-7xh7
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
1 CVE-2024-56332
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-32421
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-48068
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-55173
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-57752
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-57822
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2025-59471
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-27980
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-29057
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-41305
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44572
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44576
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44577
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44580
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44581
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-44582
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64647
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64648
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-22jq-vg5j-6vgg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3g8h-86w9-wvmq
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3h52-269p-cp9r
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3x4c-7xq6-9pq8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4342-x723-ch2f
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4xrf-jv44-h6hh
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-7m27-7ghc-44w9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-9g9p-9gw9-jx7f
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-ffhc-5mcf-pf4q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-g5qg-72qw-gw5v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-ggv3-7p47-pfv8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gx5p-jg67-6x7h
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h5c3-5r3r-rr8q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h64f-5h5j-jqjh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qpjv-v59x-3qc4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-qx2v-qp2m-jg93
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vfv6-92ff-j949
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-vh25-5764-9wcr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-wfc6-r584-vfw7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-xv57-4mr9-wg8v
Files: /repo/pnpm-lock.yaml · 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/apps/web-app/src/app/api/weather/route.ts · reported by nerlo-behavioral
27 The review call did not complete.
Rules: CVE-2025-29927, GHSA-f82v-jwr5-mffw, GHSA-mh99-v99m-4gvg and 20 more · Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml, /repo/apps/web-app/src/app/changelog/page.tsx · reported by trivy, osv-scanner, cisco-skill-scanner
24 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: GHSA-r5fr-rjxr-66jc, CVE-2026-64641, GHSA-c4j6-fc7j-m34r and 17 more · Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml, /repo/SKILL.md · reported by osv-scanner, trivy, cisco-skill-scanner
Critical vulnerabilities and potential data exfiltration risks.
The artifact includes critical vulnerabilities in its dependencies, as identified in `pnpm-lock.yaml`. Specific code in `/repo/apps/web-app/src/app/changelog/page.tsx` exhibits capabilities for file system access, which could lead to data exfiltration. Furthermore, a finding indicates potential network egress of secrets from `/repo/apps/web-app/src/app/api/weather/route.ts`.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 24 of 24; 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.