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 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 -- chadwickcasp/mlops-project
5 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
21 findings · 10.6s
v0.3.74
0 findings · 5.0s
v0.1.0
0 findings · 4.5s
v0.1.0
0 findings · 4.5s
v2.3.8
27 findings · 1.3s
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 · 0.7s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.5s
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 | Flagged45 | — | 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 ·n/a: not applicableosv-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 48 findings across every scanner that examined this package. None of the 2 findings rated critical by their scanner were dismissed.
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
1 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: TOOL_ABUSE_UNDECLARED_NETWORK · Files: /repo/repo/AGENTS.md · reported by cisco-skill-scanner
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.
7 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/image_segmentation/SKILL.md, /repo/data_sourcing/gbif/SKILL.md and 4 more · reported by cisco-skill-scanner
6 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/image_segmentation/SKILL.md, /repo/data_sourcing/gbif/SKILL.md and 3 more · reported by cisco-skill-scanner
2 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/.cursor/hooks/weekly_workflow_report.py · reported by cisco-skill-scanner
2 YARA_prompt_injection_unicode_steganography
Files: /repo/outputs/gbif_viz/sf_2026_03_occurrence_map.png · reported by cisco-skill-scanner
1 GHSA-5pcm-hx3q-hm94
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-c678-jfcj-6jmf
Critical vulnerabilities in dependencies require immediate attention.
This artifact contains critical and high-severity vulnerabilities within its dependencies, as identified in `/repo/requirements-image-segmentation.txt`. These findings indicate potential for remote code execution or other severe impacts. Additionally, medium-severity findings suggest capabilities for network egress and potential prompt injection.
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.
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-f4hp-rmr7-r7v8
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-pg7h-5qx3-wjr3
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-qfhq-4f3w-5fph
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-qr4w-53vh-m672
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-rrmf-rvhw-rf47
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-vgrw-7cvw-pwgx
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 GHSA-x3gm-94wq-g975
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/image_segmentation/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2023-183
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2024-259
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-191
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-198
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-203
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-204
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-205
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-206
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-207
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-208
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-209
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2025-41
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2026-139
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/requirements-gbif.txt · reported by osv-scanner
1 PYSEC-2026-1873
Files: /repo/requirements-gbif.txt · reported by osv-scanner
1 PYSEC-2026-1970
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/requirements-gbif.txt · reported by osv-scanner
1 PYSEC-2026-2286
Files: /repo/requirements-image-segmentation.txt · reported by osv-scanner