Loading the registry…
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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- dhis2-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 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
2 findings · 7.9s
v0.3.74
0 findings · 1.1s
v0.1.0
0 findings · 4.1s
v0.1.0
0 findings · 4.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 19, 2026 | Flagged58 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicable |
vv0.3.2
Incomplete run
0 findings · 1.9s
v0.71.0
17 findings · 0.3s
v2.3.8
63 findings · 0.9s
vv1.6.0
Incomplete run
0 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
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
| 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 82 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 51 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
1 GO-2025-4008
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4010
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4011
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4014
Files: /repo/go.mod · reported by osv-scanner
1 GO-2025-4175
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4340
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4341
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4440
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4441
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4601
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4602
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4603
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4865
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4869
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4870
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4971
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4980
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4981
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-4986
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5025
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5027
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5029
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5030
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5038
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5039
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5856
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5942
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5970
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-5972
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6089
Files: /repo/go.mod · reported by osv-scanner
1 GO-2026-6091
Files: /repo/go.mod · reported by osv-scanner
50 The review call did not complete.
Rules: CVE-2026-32285, GO-2026-4514, CVE-2026-39821 and 45 more · Files: go.mod, /repo/go.mod, /repo/SKILL.md · reported by trivy, osv-scanner, cisco-skill-scanner
1 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: MANIFEST_MISSING_LICENSE · Files: /repo/SKILL.md · reported by cisco-skill-scanner
High severity vulnerabilities detected
The artifact contains multiple high severity vulnerabilities in its dependencies, identified by CVEs in `go.mod`. A high severity finding from the `bearer` scanner indicates a potential risk within `/repo/internal/dhis2mcp/server.go`. These findings warrant immediate attention to prevent potential impacts such as remote code execution or denial of service.
Concern level assessed by the review: High. 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.