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.
5 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 -- recommendation-system
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
41 findings · 20.0s
v0.3.74
6 findings · 6.2s
v0.1.0
0 findings · 7.3s
v0.1.0
0 findings · 7.3s
v2.3.8
83 findings · 2.1s
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.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.2s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.3s
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 | Flagged35 | — | 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 130 findings across every scanner that examined this package. None of the 5 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.
7 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, MANIFEST_INVALID_NAME · Files: /repo/docs/SKILL.md, /repo/docs/changelog/SKILL.md, /repo/docs/kg_pipeline/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: HIDDEN_DATA_FILE · Files: /repo/.agents/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.
10 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/diagrams/SKILL.md, /repo/production_artifacts/SKILL.md and 7 more · reported by cisco-skill-scanner
9 HIDDEN_DATA_FILE
Files: /repo/.agents/workflows/implement.md, /repo/.agents/workflows/audit-state.md, /repo/.agents/skills/research_analyst.md and 6 more · reported by cisco-skill-scanner
8 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/diagrams/SKILL.md, /repo/production_artifacts/SKILL.md and 5 more · reported by cisco-skill-scanner
4 MANIFEST_INVALID_NAME
Files: /repo/.agents/SKILL.md, /repo/src/knowledge_graph/SKILL.md, /repo/.agents/skills/SKILL.md and 1 more · reported by cisco-skill-scanner
2 AAK-LANGCHAIN-001
Files: requirements.txt · reported by agent-audit-kit
2 AAK-LANGCHAIN-003
Files: requirements.txt · reported by agent-audit-kit
1 AAK-SSRF-TOCTOU-001
Files: requirements.txt · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 FILE_MAGIC_MISMATCH
Files: /repo/prompts_and_req/graph_pipeline_promp.txt · reported by cisco-skill-scanner
1 GHSA-5jqp-qgf6-3pvh
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-6p56-wp2h-9hxr
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-8qw9-gf7w-42x5
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-c678-jfcj-6jmf
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-f4hp-rmr7-r7v8
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-fpfv-jqm9-f5jm
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-jw8x-6495-233v
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-jxfp-4rvq-9h9m
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-qfhq-4f3w-5fph
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-rrmf-rvhw-rf47
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-vgrw-7cvw-pwgx
Files: /repo/requirements.txt · reported by osv-scanner
1 GHSA-x3gm-94wq-g975
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2022-288
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-102
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-114
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2023-74
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-153
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-227
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-228
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-229
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-250
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-251
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-252
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-259
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2024-38
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-191
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-198
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-203
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-204
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-205
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-206
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-207
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-208
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-209
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-211
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-212
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-213
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-214
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-215
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-216
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-217
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-218
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-40
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2025-41
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1237
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1238
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-139
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1517
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1518
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1812
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1872
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1873
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1909
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1970
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1976
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1977
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1980
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1981
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1982
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1983
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1984
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1985
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1986
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1987
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1988
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-212
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2192
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2193
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2285
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2286
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2288
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2289
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2290
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2555
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2562
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2563
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2564
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-373
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-598
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-76
Files: /repo/requirements.txt · reported by osv-scanner
Critical vulnerabilities in artifact dependencies
This artifact contains multiple critical and high severity vulnerabilities within its declared dependencies, primarily listed in `requirements.txt`. These issues could enable remote code execution, arbitrary file writes, or other system compromises. Additionally, specific LangChain-related findings indicate potential for insecure deserialization or sensitive data exposure.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 41; 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.