Loading the registry…
快速图表生成器 - 基于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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- quick-chart-generator
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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.1s
v2.0.11
5 findings · 9.4s
v0.3.74
12 findings · 1.7s
v0.1.0
0 findings · 4.8s
v0.1.0
0 findings · 4.8s
v2.3.8
3 findings · 1.6s
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 · 2.5s
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 20, 2026 | Flagged67 | — | agentshield: completecisco-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 20 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 6 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.
3 AAK-MCP-ATTEST-001
Files: .mcp.json, mcpServers.json, mcp-config.json · reported by agent-audit-kit
2 AAK-ANTHROPIC-SDK-001
Files: mcp_server.py, simple_mcp_server.py · reported by agent-audit-kit
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: mcp.json, requirements.txt · reported by agent-audit-kit
1 AAK-MCP-003
Files: mcpServers.json · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: requirements.txt · reported by agent-audit-kit
1 AAK-SECRET-007
Files: mcpServers.json · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: package.json · reported by agent-audit-kit
1 PYSEC-2026-1617
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/requirements.txt · reported by osv-scanner
6 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, HIDDEN_DATA_FILE, PYCACHE_FILES_DETECTED and 2 more · Files: SECURITY.md, /repo/.rules/dev.mdc, /repo/.rules/pm.mdc and 2 more · reported by agent-audit-kit, cisco-skill-scanner
High-severity vulnerabilities in SDKs and dependencies detected.
The artifact contains multiple high-severity vulnerabilities, including issues within the Anthropic and MCP SDKs, as well as several CVEs in dependencies listed in `requirements.txt`. Specific configuration files like `mcp.json` and `mcpServers.json` also present high-severity findings. These issues could lead to various risks, including potential credential access or unauthorized operations.
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.