Loading the registry…
Add your description here
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 -- assessmate
6 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.
v2.0.11
7 findings · 7.3s
v0.3.74
1 finding · 1.8s
v0.1.0
0 findings · 3.2s
v0.1.0
1 finding · 3.2s
v0.71.0
40 findings · 0.4s
v2.3.8
40 findings · 8.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
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.9s
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 | Flagged41 | — | agentshield ·n/a: not applicablecisco-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 89 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.
4 DATA_EXFIL_JS_NETWORK
Files: /repo/frontend/src/api.js · reported by cisco-skill-scanner
2 GHSA-4xgf-cpjx-pc3j
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-g7r4-m6w7-qqqr
Files: /repo/frontend/package-lock.json, frontend/package-lock.json · reported by osv-scanner, trivy
2 GHSA-jm82-fx9c-mx94
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
1 AAK-LEGAL-002
Files: frontend/package.json · reported by agent-audit-kit
1 CVE-2025-3000
Files: uv.lock · reported by trivy
1 CVE-2026-12061
Files: uv.lock · reported by trivy
1 CVE-2026-12072
Files: uv.lock · reported by trivy
1 CVE-2026-12074
Files: uv.lock · reported by trivy
1 CVE-2026-12075
Files: uv.lock · reported by trivy
1 CVE-2026-12243
Files: uv.lock · reported by trivy
1 CVE-2026-54058
Files: uv.lock · reported by trivy
1 CVE-2026-54059
Files: uv.lock · reported by trivy
1 CVE-2026-54060
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-54293
Files: uv.lock · reported by trivy
1 CVE-2026-55379
Files: uv.lock · reported by trivy
1 CVE-2026-55380
Files: uv.lock · reported by trivy
1 CVE-2026-55798
Files: uv.lock · reported by trivy
1 CVE-2026-59197
Files: uv.lock · reported by trivy
1 CVE-2026-59198
Files: uv.lock · reported by trivy
1 CVE-2026-59199
Files: uv.lock · reported by trivy
1 CVE-2026-59200
Files: uv.lock · reported by trivy
1 CVE-2026-59203
Files: uv.lock · reported by trivy
1 CVE-2026-59204
Files: uv.lock · reported by trivy
1 CVE-2026-59205
Files: uv.lock · reported by trivy
1 CVE-2026-59881
Files: uv.lock · reported by trivy
1 CVE-2026-59890
Files: uv.lock · reported by trivy
1 CVE-2026-59935
Files: uv.lock · reported by trivy
1 CVE-2026-59936
Files: uv.lock · reported by trivy
1 CVE-2026-59937
Files: uv.lock · reported by trivy
1 CVE-2026-59938
Files: uv.lock · reported by trivy
1 CVE-2026-67213
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-67214
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-69153
Files: frontend/package-lock.json · reported by trivy
1 CVE-2026-69243
Files: uv.lock · reported by trivy
1 CVE-2026-69244
Files: uv.lock · reported by trivy
1 CVE-2026-71554
Files: uv.lock · reported by trivy
1 CVE-2026-71852
Files: uv.lock · reported by trivy
1 CVE-2026-71870
Files: uv.lock · reported by trivy
1 CVE-2026-73646
Files: frontend/package-lock.json · reported by trivy
1 FILE_MAGIC_MISMATCH
Files: /repo/frontend/vite.config.js · reported by cisco-skill-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/frontend/package-lock.json · reported by osv-scanner
1 GHSA-rrmf-rvhw-rf47
Files: /repo/uv.lock · reported by osv-scanner
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 opt.nerlo-rules.nerlo-install-pipe-to-shell
Files: /repo/commands.txt · reported by nerlo-install-instruction
1 PYSEC-2026-2078
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3447
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3452
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3546
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3547
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3581
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3582
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3583
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3584
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3610
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3611
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3612
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3613
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3628
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3655
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3656
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-597
Files: /repo/uv.lock · reported by osv-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 CVE-2026-54282
Files: uv.lock · reported by trivy
Multiple high-severity vulnerabilities and shell execution risk identified.
The artifact contains numerous high-severity vulnerabilities in its dependencies, affecting both Python and frontend components as indicated in `uv.lock` and `package-lock.json`. A critical finding indicates that the installation instructions in `commands.txt` involve piping to a shell, which can lead to arbitrary shell execution during installation. These issues collectively present a significant risk of system compromise.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 48; 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.