GraphCanon rates GAGE "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 43 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Last scanned today (deps profile). Status: 89 low - 89 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 GAGE as safe - review maintenance, provenance, and scan findings on this page before adopting.

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

Does GAGE have known security vulnerabilities?

Last scanned today (deps profile). Status: 89 low - 89 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 GAGE trust report updated?

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

What does GraphCanon never claim about GAGE?

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

How does GraphCanon assess trust for GAGE?

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/GAGE/Trust report

Trust and health report

GAGE - trust report

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

GraphCanon updated today · GitHub synced today

Maintenance

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

Steady60% signal

last push 43d ago · last release 1mo · 3 releases (90d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 986938784
Not a fork
Verified publisher: organization account
Computed today

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: today
Scanner: osv@v1
Stored findings: 89

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-9hjg-9r4m-mvj7

requests@2.31.0 · osv@v1

requirements.txt

GHSA-9wx4-h78v-vm56

requests@2.31.0 · osv@v1

requirements.txt

GHSA-gc5v-m9x4-r6x2

requests@2.31.0 · osv@v1

requirements.txt

PYSEC-2026-1872

requests@2.31.0 · osv@v1

requirements.txt

PYSEC-2026-1873

requests@2.31.0 · osv@v1

requirements.txt

PYSEC-2026-2275

requests@2.31.0 · osv@v1

requirements.txt

GHSA-cpwx-vrp4-4pq7

jinja2@3.1.0 · osv@v1

requirements.txt

GHSA-gmj6-6f8f-6699

jinja2@3.1.0 · osv@v1

requirements.txt

GHSA-h5c8-rqwp-cp95

jinja2@3.1.0 · osv@v1

requirements.txt

GHSA-h75v-3vvj-5mfj

jinja2@3.1.0 · osv@v1

requirements.txt

GHSA-q2x7-8rv6-6q7h

jinja2@3.1.0 · osv@v1

requirements.txt

PYSEC-2026-1471

jinja2@3.1.0 · osv@v1

requirements.txt

PYSEC-2026-1472

jinja2@3.1.0 · osv@v1

requirements.txt

PYSEC-2026-1473

jinja2@3.1.0 · osv@v1

requirements.txt

PYSEC-2026-1474

jinja2@3.1.0 · osv@v1

requirements.txt

PYSEC-2026-1475

jinja2@3.1.0 · osv@v1

requirements.txt

GHSA-fhhq-h4hg-549x

modelscope@1.13.0 · osv@v1

requirements.txt

PYSEC-2026-2663

modelscope@1.13.0 · osv@v1

requirements.txt

GHSA-4xpc-pv4p-pm3w

litellm@1.83.14 · osv@v1

requirements.txt

PYSEC-2026-388

litellm@1.83.14 · osv@v1

requirements.txt

GHSA-9h52-p55h-vw2f

mcp@1.19.0 · osv@v1

requirements.txt

PYSEC-2026-1617

mcp@1.19.0 · osv@v1

requirements.txt

GHSA-rrmf-rvhw-rf47

torch@2.11.0+cu129 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-37q5-v5qm-c9v8

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-6rvg-6v2m-4j46

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-fgcw-684q-jj6r

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-fpwr-67px-3qhx

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-hxxf-235m-72v3

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-jjph-296x-mrcr

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-q2wp-rjmx-x6x9

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-qq3j-4f4f-9583

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-qxrp-vhvm-j765

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-wrfc-pvp9-mr9g

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2024-227

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2024-228

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2024-229

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2025-40

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1978

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1982

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1984

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1985

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1987

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-2288

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-2289

transformers@4.36.0 · osv@v1

requirements.txt

PYSEC-2026-2290

transformers@4.36.0 · osv@v1

requirements.txt

GHSA-3f63-hfp8-52jq

Pillow@10.0.0 · osv@v1

requirements.txt

GHSA-44wm-f244-xhp3

Pillow@10.0.0 · osv@v1

requirements.txt

GHSA-j7hp-h8jx-5ppr

Pillow@10.0.0 · osv@v1

requirements.txt

GHSA-r73j-pqj5-w3x7

Pillow@10.0.0 · osv@v1

requirements.txt

GHSA-wjx4-4jcj-g98j

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2023-175

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-165

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-1793

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-1794

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-2253

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-2254

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-2255

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-2256

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-2257

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-2874

Pillow@10.0.0 · osv@v1

requirements.txt

PYSEC-2026-457

Pillow@10.0.0 · osv@v1

requirements.txt

GHSA-qmgc-5h2g-mvrw

filelock@3.13.0 · osv@v1

requirements.txt

GHSA-w853-jp5j-5j7f

filelock@3.13.0 · osv@v1

requirements.txt

PYSEC-2026-1374

filelock@3.13.0 · osv@v1

requirements.txt

PYSEC-2026-1375

filelock@3.13.0 · osv@v1

requirements.txt

GHSA-jh2j-j4j9-crg3

opencv-python-headless@4.8.0 · osv@v1

requirements.txt

PYSEC-2023-184

opencv-python-headless@4.8.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/hithink-research-gage/trust.

Common questions

Is GAGE maintained?: GraphCanon rates GAGE "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 43 days ago. 3 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
Is GAGE safe to use?: Last scanned today (deps profile). Status: 89 low - 89 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 GAGE as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is GAGE a fork?: No. GAGE is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does GAGE have known security vulnerabilities?: Last scanned today (deps profile). Status: 89 low - 89 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 GAGE trust report updated?: Trust signals refresh on GitHub ingest/refresh cycles and optional dependency/MCP scans. This report was computed today (methodology github_public_v1).
What does GraphCanon never claim about GAGE?: We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for GAGE. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for GAGE?: 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.