Loading the registry…
A chatbot for searching best medication prices using MCP
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.
12 critical findings reported by trivy, osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- medication-price-chatbot
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
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.7s
v2.0.11
25 findings · 9.9s
v0.3.74
8 findings · 4.2s
v0.1.0
0 findings · 6.7s
v0.1.0
0 findings · 6.7s
v0.71.0
138 findings · 0.5s
v2.3.8
220 findings · 9.4s
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 20, 2026 | Flagged42 | — | 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 391 findings across every scanner that examined this package. None of the 12 findings rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 263 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.
1 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: RESOURCE_ABUSE_INFINITE_LOOP · Files: /repo/backend/examples/advanced_scenarios.py · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
3 GHSA-23c5-xmqv-rm74
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-3ppc-4f35-3m26
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-7r86-cg39-jmmj
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
2 CVE-2026-45623
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-73646
Files: frontend/pnpm-lock.yaml · reported by trivy
2 GHSA-5j59-xgg2-r9c4
Files: /repo/frontend/pnpm-lock.yaml, frontend/pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-6g55-p6wh-862q
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-8h8q-6873-q5fj
Files: frontend/pnpm-lock.yaml, /repo/frontend/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-c2c7-rcm5-vvqj
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-c2jp-c369-7pvx
Files: /repo/backend/requirements.txt, /repo/backend/uv.lock · reported by osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-q4gf-8mx6-v5v3
Files: frontend/pnpm-lock.yaml, /repo/frontend/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-r28c-9q8g-f849
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
2 GHSA-rgw5-rvv9-x895
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
2 PYSEC-2026-2141
Files: /repo/backend/requirements.txt, /repo/backend/uv.lock · reported by osv-scanner
2 PYSEC-2026-2474
Files: /repo/backend/requirements.txt, /repo/backend/uv.lock · reported by osv-scanner
2 PYSEC-2026-338
Files: /repo/backend/requirements.txt, /repo/backend/uv.lock · reported by osv-scanner
2 PYSEC-2026-3553
Files: /repo/backend/requirements.txt, /repo/backend/uv.lock · reported by osv-scanner
1 CVE-2024-46982
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2024-51479
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2025-29927
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2025-58754
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2025-59420
Files: backend/uv.lock · reported by trivy
1 CVE-2025-62727
Files: backend/uv.lock · reported by trivy
1 CVE-2025-64756
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2025-66418
Files: backend/uv.lock · reported by trivy
1 CVE-2025-66471
Files: backend/uv.lock · reported by trivy
1 CVE-2025-7783
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-21441
Files: backend/uv.lock · reported by trivy
1 CVE-2026-25639
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27903
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27904
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27962
Files: backend/uv.lock · reported by trivy
1 CVE-2026-28490
Files: backend/uv.lock · reported by trivy
1 CVE-2026-32871
Files: backend/uv.lock · reported by trivy
1 CVE-2026-33671
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-42035
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-42264
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-42561
Files: backend/uv.lock · reported by trivy
1 CVE-2026-44486
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44487
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44488
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44494
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44495
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44573
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44578
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-48818
Files: backend/uv.lock · reported by trivy
1 CVE-2026-53539
Files: backend/uv.lock · reported by trivy
1 CVE-2026-59950
Files: backend/uv.lock · reported by trivy
1 CVE-2026-67213
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-69247
Files: backend/uv.lock · reported by trivy
1 CVE-2026-69249
Files: backend/uv.lock · reported by trivy
1 GHSA-25h7-pfq9-p65f
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-35jp-ww65-95wh
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-36qx-fr4f-26g5
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3g43-6gmg-66jw
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4hjh-wcwx-xvwj
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-537c-gmf6-5ccf
Files: backend/uv.lock · reported by trivy
1 GHSA-5j98-mcp5-4vw2
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f82v-jwr5-mffw
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fjxv-7rqg-78g4
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fr5h-rqp8-mj6g
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-gp8f-8m3g-qvj9
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-h25m-26qc-wcjf
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-hfxv-24rg-xrqf
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwv6-3258-q52c
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8qp-cvcw-x6jj
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rcfx-77hg-w2wv
Files: backend/uv.lock · reported by trivy
1 GHSA-rf6f-7fwh-wjgh
Files: /repo/frontend/pnpm-lock.yaml · reported by osv-scanner
1 PYSEC-2024-232
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2024-38
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1101
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-1200
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-1283
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-1617
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-2098
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2102
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2104
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2105
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2106
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2111
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2112
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2113
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-2116
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-2117
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-237
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-287
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-3545
Files: /repo/backend/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/backend/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/backend/uv.lock · reported by osv-scanner
209 The review budget for this scan was already spent before these findings were reached.
Rules: GHSA-m99w-x7hq-7vfj, GHSA-pmwg-cvhr-8vh7, CVE-2026-64645 and 167 more · Files: /repo/frontend/pnpm-lock.yaml, frontend/pnpm-lock.yaml, backend/uv.lock and 22 more · reported by osv-scanner, trivy, agent-audit-kit and 1 more
54 The review call did not complete.
Rules: RESOURCE_ABUSE_INFINITE_LOOP, GHSA-3jxr-9vmj-r5cp, GHSA-537c-gmf6-5ccf and 47 more · Files: /repo/backend/cache.py, /repo/backend/rate_limit.py, /repo/frontend/pnpm-lock.yaml and 4 more · reported by cisco-skill-scanner, osv-scanner, trivy
Critical vulnerabilities and resource abuse found.
The artifact includes multiple critical vulnerabilities in its backend and frontend dependencies, identified in `requirements.txt`, `uv.lock`, and `pnpm-lock.yaml`. High-severity findings include potential resource abuse via infinite loops in `cache.py` and `rate_limit.py`. Additional high-severity vulnerabilities are present across various backend dependencies.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 25; 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.