Grafyx
PYPI · GRAFYX-MCP · SCANNED AUG 3
Real-time codebase graph for AI assistants: call graphs, dependencies, symbol lookup.
Available components
Recent critical change
CVE-2026-42284 affects this package (3 Aug 2026). See the changelog before you install this server.
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 →
Supply Chain Security24
- Malware scan not yet available for this package.Unverified
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 26 of 206 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
pypi · grafyx-mcp
claude mcp add bilal07karadeniz-grafyx -- uvx grafyx-mcp
codex mcp add bilal07karadeniz-grafyx -- uvx grafyx-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bilal07karadeniz-grafyx": {
"type": "local",
"command": [
"uvx",
"grafyx-mcp"
],
"enabled": true
}
}
} openclaw mcp add bilal07karadeniz-grafyx --command uvx --arg grafyx-mcp
mcp_servers:
bilal07karadeniz-grafyx:
command: "uvx"
args: ["grafyx-mcp"] {
"mcpServers": {
"bilal07karadeniz-grafyx": {
"command": "uvx",
"args": [
"grafyx-mcp"
]
}
}
} 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.
- 3 Aug 26 −13
- CVE-2026-42284 affects this package: high ▼ critical
- Known CVEs: unverified → fail ▼ critical
- Score status: scored → failed ▼ critical
- Dependency health: unverified → 0.95 ▲ functional
- 2 Aug 26 13
First indexed and scored.
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 3 Aug 2026 · Analysed pypi/[email protected]
Provenance none
Ecosystem: pypi · Outcome: none
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Vulnerabilities 27 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2f96-g7mh-g2hx | CVE-2026-67325 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-3rp5-jjmw-4wv2 | high | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H | yes | |
| GHSA-6p8h-3wgx-97gf | high | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | yes | |
| GHSA-7545-fcxq-7j24 | CVE-2026-44243 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| GHSA-94p4-4cq8-9g67 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes | |
| GHSA-956x-8gvw-wg5v | CVE-2026-67323 | high | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-fjr4-x663-mwxc | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes | |
| GHSA-mv93-w799-cj2w | CVE-2026-67326 | high | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-r9mr-m37c-5fr3 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes | |
| GHSA-rpm5-65cw-6hj4 | CVE-2026-42215 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-rwj8-pgh3-r573 | CVE-2026-67322 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-v87r-6q3f-2j67 | CVE-2026-44244 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-x2qx-6953-8485 | CVE-2026-42284 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2160 | CVE-2026-42215 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2161 | CVE-2026-42284 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2162 | CVE-2026-44243 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H | yes |
| PYSEC-2026-2163 | CVE-2026-44244 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-82w8-qh3p-5jfq | CVE-2026-54283 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-86qp-5c8j-p5mr | CVE-2026-48710 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-jp82-jpqv-5vv3 | CVE-2026-54282 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-wqp7-x3pw-xc5r | CVE-2026-48818 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-x746-7m8f-x49c | CVE-2026-48817 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-161 | CVE-2026-48710 | none | yes | |
| PYSEC-2026-2280 | CVE-2026-48817 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-2281 | CVE-2026-48818 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| PYSEC-2026-248 | CVE-2026-54282 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| PYSEC-2026-249 | CVE-2026-54283 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Dependencies 206 packages
206 packages in the resolved dependency tree · 23 stale · 4 without a linked repository.
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.
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.