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 -- mocun496/mcp-media-extract
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
5 findings · 7.2s
v0.3.74
3 findings · 1.1s
v0.1.0
0 findings · 3.5s
v0.1.0
0 findings · 3.5s
v2.3.8
23 findings · 1.4s
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.0s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
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 | Flagged46 | — | 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 31 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.
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/media_extract_tool/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/media_extract_tool/SKILL.md · reported by cisco-skill-scanner
1 AAK-MCP-006
Files: .cursor/mcp.json · reported by agent-audit-kit
1 AAK-MCP-ATTEST-001
Files: .cursor/mcp.json · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: media_extract_tool/requirements.txt · reported by agent-audit-kit
1 MANIFEST_INVALID_NAME
Files: /repo/media_extract_tool/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2023-175
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1616
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1618
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-165
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1793
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1794
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2253
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2254
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2255
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2256
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2257
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2874
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3451
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3453
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3454
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3493
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3494
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3495
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3496
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
1 PYSEC-2026-457
Files: /repo/media_extract_tool/requirements.txt · reported by osv-scanner
Critical vulnerabilities in dependencies require immediate review.
The artifact contains dependencies with critical and high-severity vulnerabilities, primarily identified in the `requirements.txt` file. Specifically, PYSEC-2026-457 is a critical vulnerability that warrants immediate attention. Multiple high-severity vulnerabilities, such as AAK-MCP-SDK-CVE-2026-52869-001 and various PYSEC-2026 findings, are also present. These issues indicate potential risks within the installed code's foundational components.
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.