Loading the registry…
Model Context Protocol (MCP) server for SonarCloud integration - provides AI tools for querying code quality metrics, issues, and project data
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.
npm: community-sonarcloud-mcp-server @ 1.1.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- community-sonarcloud-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.
v1.4.0
0 findings · 1.0s
v2.0.11
5 findings · 12.9s
v0.3.74
5 findings · 1.8s
v0.1.0
2 findings · 5.8s
v0.1.0
0 findings · 5.8s
v0.1.0
0 findings · 12.5s
v0.71.0
76 findings · 0.4s
v2.3.8
76 findings · 12.3s
vv0.3.2
No Go packages were 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 19, 2026 | Flagged44 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: 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 164 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 32 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.
2 GHSA-26pp-8wgv-hjvm
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-42h9-826w-cgv3
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-frvp-7c67-39w9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mwf2-3pr3-8698
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-r4q5-vmmm-2653
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-v8w9-8mx6-g223
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
1 AAK-ANTHROPIC-SDK-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: src/index.ts · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2025-62718
Files: package-lock.json · reported by trivy
1 CVE-2026-12143
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-18446
Files: package-lock.json · reported by trivy
1 CVE-2026-29045
Files: package-lock.json · reported by trivy
1 CVE-2026-29085
Files: package-lock.json · reported by trivy
1 CVE-2026-29086
Files: package-lock.json · reported by trivy
1 CVE-2026-30827
Files: package-lock.json · reported by trivy
1 CVE-2026-39406
Files: package-lock.json · reported by trivy
1 CVE-2026-39407
Files: package-lock.json · reported by trivy
1 CVE-2026-39408
Files: package-lock.json · reported by trivy
1 CVE-2026-39409
Files: package-lock.json · reported by trivy
1 CVE-2026-39410
Files: package-lock.json · reported by trivy
1 CVE-2026-40175
Files: package-lock.json · reported by trivy
1 CVE-2026-42034
Files: package-lock.json · reported by trivy
1 CVE-2026-42036
Files: package-lock.json · reported by trivy
1 CVE-2026-42037
Files: package-lock.json · reported by trivy
1 CVE-2026-42038
Files: package-lock.json · reported by trivy
1 CVE-2026-42039
Files: package-lock.json · reported by trivy
1 CVE-2026-42040
Files: package-lock.json · reported by trivy
1 CVE-2026-42041
Files: package-lock.json · reported by trivy
1 CVE-2026-42042
Files: package-lock.json · reported by trivy
1 CVE-2026-42043
Files: package-lock.json · reported by trivy
1 CVE-2026-42044
Files: package-lock.json · reported by trivy
1 CVE-2026-42338
Files: package-lock.json · reported by trivy
1 CVE-2026-44455
Files: package-lock.json · reported by trivy
1 CVE-2026-44456
Files: package-lock.json · reported by trivy
1 CVE-2026-44457
Files: package-lock.json · reported by trivy
1 CVE-2026-44458
Files: package-lock.json · reported by trivy
1 CVE-2026-44459
Files: package-lock.json · reported by trivy
1 CVE-2026-44486
Files: package-lock.json · reported by trivy
1 CVE-2026-44487
Files: package-lock.json · reported by trivy
1 CVE-2026-44488
Files: package-lock.json · reported by trivy
1 CVE-2026-44490
Files: package-lock.json · reported by trivy
1 CVE-2026-44495
Files: package-lock.json · reported by trivy
1 CVE-2026-44496
Files: package-lock.json · reported by trivy
1 CVE-2026-47673
Files: package-lock.json · reported by trivy
1 CVE-2026-47674
Files: package-lock.json · reported by trivy
1 CVE-2026-47675
Files: package-lock.json · reported by trivy
1 CVE-2026-47676
Files: package-lock.json · reported by trivy
1 CVE-2026-4923
Files: package-lock.json · reported by trivy
1 CVE-2026-54286
Files: package-lock.json · reported by trivy
1 CVE-2026-54287
Files: package-lock.json · reported by trivy
1 CVE-2026-54288
Files: package-lock.json · reported by trivy
1 CVE-2026-54289
Files: package-lock.json · reported by trivy
1 CVE-2026-54290
Files: package-lock.json · reported by trivy
1 CVE-2026-56761
Files: package-lock.json · reported by trivy
1 CVE-2026-59895
Files: package-lock.json · reported by trivy
1 CVE-2026-59896
Files: package-lock.json · reported by trivy
1 CVE-2026-59897
Files: package-lock.json · reported by trivy
1 CVE-2026-6322
Files: package-lock.json · reported by trivy
1 CVE-2026-69192
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
Files: package-lock.json · reported by trivy
1 CVE-2026-71848
Files: package-lock.json · reported by trivy
1 CVE-2026-71849
Files: package-lock.json · reported by trivy
1 CVE-2026-71850
Files: package-lock.json · reported by trivy
1 CVE-2026-8723
Files: package-lock.json · reported by trivy
1 GHSA-27v5-c462-wpq7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2gcr-mfcq-wcc3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-35jp-ww65-95wh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3hrh-pfw6-9m5x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3p68-rc4w-qgx5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-3w6x-2g7m-8v23
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-445q-vr5w-6q77
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-458j-xx4x-4375
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-46wh-pxpv-q5gq
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5c9x-8gcm-mpgx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5pq2-9x2x-5p6w
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-69xw-7hcm-h432
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6chq-wfr3-2hj9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-898c-q2cr-xwhg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-92pp-h63x-v22m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-9vqf-7f2p-gf9v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f577-qrjj-4474
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fvcv-3m26-pcqx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hm8q-7f3q-5f36
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hvrm-45r6-mjfj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j5f8-grm9-p9fc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-j6c9-x7qj-28xf
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m7pr-hjqh-92cm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p6xx-57qc-3wxr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p77w-8qqv-26rm
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-pmwg-cvhr-8vh7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8mj-m7cp-5q26
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8qp-cvcw-x6jj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-qp7p-654g-cw7p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r5rp-j6wh-rvv4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-rv63-4mwf-qqc2
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v2v4-37r5-5v8g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v39h-62p7-jpjc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-vf2m-468p-8v99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w62v-xxxg-mg59
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-w9j2-pvgh-6h63
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wgpf-jwqj-8h8p
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wmmm-f939-6g9c
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-wwfh-h76j-fc44
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xf4j-xp2r-rqqx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xgm2-5f3f-mvvc
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xhjh-pmcv-23jw
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xpcf-pg52-r92g
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xrhx-7g5j-rcj5
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xx6v-rp6x-q39c
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
26 The review call did not complete.
Rules: opt.nerlo-rules.nerlo-js-secret-to-network-egress, GHSA-62hf-57xw-28j9, CVE-2026-42033 and 22 more · Files: /repo/src/index.ts, /repo/package-lock.json, package-lock.json · reported by nerlo-behavioral, osv-scanner, trivy
3 The review budget for this scan was already spent before these findings were reached.
Rules: DATA_EXFIL_JS_NETWORK, MANIFEST_MISSING_LICENSE · Files: /repo/src/index.ts, /repo/SKILL.md · reported by cisco-skill-scanner
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, AAK-OAUTH-008 · Files: SECURITY.md, sonarcloud-config.example.json · reported by agent-audit-kit
1 The model did not answer for these findings.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION · Files: /repo/SKILL.md · reported by cisco-skill-scanner
Network egress with secrets and critical dependency vulnerabilities.
The artifact is capable of network egress, potentially transmitting secrets. It also integrates an AI SDK, indicating further external communication. Additionally, multiple high-severity vulnerabilities are present in its third-party dependencies. These issues collectively pose a significant risk of data exposure or system compromise.
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.
Showing 25 of 48; the rest are in the per-scanner reports above.