Is MGDebugger maintained?

GraphCanon rates MGDebugger "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 395 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

Is MGDebugger safe to use?

Last scanned 1mo (deps profile). Status: 111 low - 111 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify MGDebugger as safe - review maintenance, provenance, and scan findings on this page before adopting.

Is MGDebugger a fork?

No. MGDebugger is not flagged as a fork in GitHub metadata at the time of the last refresh.

Does MGDebugger have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 111 low - 111 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.

How often is the MGDebugger trust report updated?

Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).

What does GraphCanon never claim about MGDebugger?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MGDebugger. Signals are sourced heuristics with explicit limits - see trust methodology (https://www.graphcanon.com/trust-methodology).

How does GraphCanon assess trust for MGDebugger?

Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology (https://www.graphcanon.com/trust-methodology) for full scope and limits.

Home/MGDebugger/Trust report

Trust and health report

MGDebugger - trust report

Sourced, dated trust signals - maintenance label posture, repository provenance, and security scan status. Not a composite safety grade.

GraphCanon updated 2w · GitHub synced 2w · 26 views this month

Maintenance

Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.

Dormant18% signal

last push 395d ago

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 863927529
Not a fork
Personal account
Computed 2w

Security intelligence

Source-by-source security scan results from public intelligence providers. Missing, partial, or failed queries are shown explicitly and are not treated as clean.

OSV dependency advisories

Published findings

Last query: 1mo
Scanner: osv@v1
Stored findings: 111

View source evidence

deps.dev advisories

Not queried

Scanner: deps.dev@v1

View source evidence

OpenSSF Scorecard

Not queried

Scanner: openssf-scorecard@v1

Weekly public scans omit some checks at scale.

View source evidence

Dependency advisories (deduplicated)

GHSA-7g5w-pq96-8c5w

flash-attn@2.5.9.post121 · osv@v1

requirements.txt

GHSA-3749-ghw9-m3mg

torch@2.4.0 · osv@v1

requirements.txt

GHSA-53q9-r3pm-6pq6

torch@2.4.0 · osv@v1

requirements.txt

GHSA-887c-mr87-cxwp

torch@2.4.0 · osv@v1

requirements.txt

GHSA-c678-jfcj-6jmf

torch@2.4.0 · osv@v1

requirements.txt

GHSA-f4hp-rmr7-r7v8

torch@2.4.0 · osv@v1

requirements.txt

GHSA-qfhq-4f3w-5fph

torch@2.4.0 · osv@v1

requirements.txt

GHSA-rrmf-rvhw-rf47

torch@2.4.0 · osv@v1

requirements.txt

GHSA-vgrw-7cvw-pwgx

torch@2.4.0 · osv@v1

requirements.txt

GHSA-x3gm-94wq-g975

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2024-259

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-191

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-198

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-203

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-204

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-205

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-206

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-207

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-208

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-209

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-41

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2026-139

torch@2.4.0 · osv@v1

requirements.txt

PYSEC-2026-1970

torch@2.4.0 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-6rvg-6v2m-4j46

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-fpwr-67px-3qhx

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-hxxf-235m-72v3

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-jjph-296x-mrcr

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-q2wp-rjmx-x6x9

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-qq3j-4f4f-9583

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-qxrp-vhvm-j765

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-wrfc-pvp9-mr9g

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2024-227

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2024-228

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2024-229

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2025-40

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1982

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1984

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1985

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1987

transformers@4.44.2 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.44.2 · osv@v1

requirements.txt

GHSA-3f6c-7fw2-ppm4

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-3mwp-wvh9-7528

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-3ww4-5jv9-j5gm

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-4qjh-9fv9-r85r

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-5jv2-g5wq-cmr4

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-5vqr-wprc-cpp7

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-69j4-grxj-j64p

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-6fvq-23cw-5628

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-6pr9-rp53-2pmc

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-7h4p-rffg-7823

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-8fr4-5q9j-m8gm

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-94f4-hr76-p5j6

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-98f3-hwg4-4rf7

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-9f8f-2vmf-885j

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-9pcc-gvx5-r5wm

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-cj47-qj6g-x7r4

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-ggpf-24jw-3fcw

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-hgg8-fqqc-vfmw

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-mgrm-fgjv-mhv8

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-pgr7-mhp5-fgjp

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-pmqf-x6x8-p7qw

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-q8gq-377p-jq3r

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-qh4c-xf7m-gxfc

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-rh4j-5rhw-hr54

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-rm76-4mrf-v9r8

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-rxc4-3w6r-4v47

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-wr9h-g72x-mwhm

vllm@0.6.0 · osv@v1

requirements.txt

GHSA-x368-4g9h-fvv4

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-222

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-223

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-42

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-43

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-50

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-53

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-58

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2025-62

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2011

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2012

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2013

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2015

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2016

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2017

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2019

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2020

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2021

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-2026

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-226

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-227

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-566

vllm@0.6.0 · osv@v1

requirements.txt

PYSEC-2026-568

vllm@0.6.0 · osv@v1

requirements.txt

Method and caveats: these are sourced, dated heuristics from public GitHub data and external security intelligence providers. A status like "no published findings from this source" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/yerbapage-mgdebugger/trust.

Common questions

Is MGDebugger maintained?: GraphCanon rates MGDebugger "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 395 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is MGDebugger safe to use?: Last scanned 1mo (deps profile). Status: 111 low - 111 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report. GraphCanon does not certify MGDebugger as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is MGDebugger a fork?: No. MGDebugger is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does MGDebugger have known security vulnerabilities?: Last scanned 1mo (deps profile). Status: 111 low - 111 low finding(s) in the latest scan. GraphCanon does not claim the project is safe or vulnerability-free; review findings on the trust report.
How often is the MGDebugger trust report updated?: Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed 2w (methodology github_public_v1).
What does GraphCanon never claim about MGDebugger?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MGDebugger. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for MGDebugger?: Signals are sourced from public GitHub metadata and optional dependency/MCP manifest scans, each tagged with methodology version and computed date. GraphCanon does not publish a composite safety grade. Read trust methodology for full scope and limits.