Chart Color Audit
NPM · CHART-COLOR-AUDIT
CI-friendly accessibility audit for chart color palettes: WCAG contrast, CVD simulation, OKLab ΔE.
Available components
Last scanned (16 hours ago)
Scores higher than 92% of npm servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to socraticstatic/chart-color-audit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 415 tokens (~207/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- Security disclosure: fail → unverified ▼ functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
- 18 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/chart-color-audit@0.2.5
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | socraticstatic/chart-color-audit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/socraticstatic/chart-color-audit/.github/workflows/release.yml@refs/tags/v0.2.5 |
| Rekor log index | 3077765413 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6ec5f43ae9df9566ce64173eaad3028c3167d8b63f683898a8f3b5d5bf012de397ed3d7f2d7d0d9d5f33053ea569b745875a939c5061d030f447c7e12 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_palette Audit a chart color palette ~180
Audit chart colors for accessibility: pairwise OKLab ΔE separation under normal vision, deuteranopia, protanopia, tritanopia (published Machado 2009 matrices) and grayscale, plus WCAG 2.2 SC 1.4.11 non-text contrast (≥3:1) against the background. Returns per-vision findings with human-word bands and a pass/fail verdict with reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | Background color the chart marks render on. |
| colors | array | yes | Palette colors in slot order — any CSS color syntax (#hex, hsl(), rgb(), named). |
| mode | string | – | Floors preset. perceptual (default) fails what an eye can't tell apart (ΔE<2); redundant-encodings for palettes paired with dash/decal/shape channels; strict demands clear separation. |
No output schema declared.
No examples provided.
audit_tokens Audit chart tokens from a config file ~65
Run the same audit against a chartaudit.config.json on disk — the config names a CSS or design-tokens file plus which tokens are the categorical palette, background, and semantic roles.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string | yes | Absolute or cwd-relative path to chartaudit.config.json. |
No output schema declared.
No examples provided.
How do I install the Chart Color Audit MCP server?
Chart Color Audit runs locally as an npm package, launched with npx -y chart-color-audit mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · chart-color-audit
claude mcp add socraticstatic-chart-color-audit -- npx -y chart-color-audit mcp
What is the Chart Color Audit MCP server?
Chart Color Audit is an MCP server listed in the public MCP registry as io.github.socraticstatic/chart-color-audit. CI-friendly accessibility audit for chart color palettes: WCAG contrast, CVD simulation, OKLab ΔE. This page covers its npm package (chart-color-audit).
Is the Chart Color Audit MCP server safe to use?
Chart Color Audit scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Chart Color Audit MCP server expose?
Chart Color Audit exposes 2 tools: audit_palette, audit_tokens. Their descriptions and schemas cost roughly 245 tokens of context every time the server is loaded.
Is the Chart Color Audit MCP server still maintained?
Chart Color Audit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Chart Color Audit MCP server under?
Chart Color Audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Chart Color Audit MCP server?
VerifyMCP ran 16 checks on Chart Color Audit, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.