Is MixEval maintained?

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

Is MixEval safe to use?

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

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

Does MixEval have known security vulnerabilities?

Last scanned 1mo (deps profile). Status: 109 low - 109 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 MixEval trust report updated?

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

What does GraphCanon never claim about MixEval?

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

How does GraphCanon assess trust for MixEval?

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

Trust and health report

MixEval - trust report

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

GraphCanon updated 3w · GitHub synced 3w · 30 views this month

Maintenance

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

Dormant18% signal

last push 625d ago

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 808982778
Not a fork
Personal account
Computed 3w

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: 109

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-qmgc-5h2g-mvrw

filelock@3.15.4 · osv@v1

requirements.txt

GHSA-w853-jp5j-5j7f

filelock@3.15.4 · osv@v1

requirements.txt

PYSEC-2026-1374

filelock@3.15.4 · osv@v1

requirements.txt

PYSEC-2026-1375

filelock@3.15.4 · osv@v1

requirements.txt

GHSA-vqfr-h8mv-ghfj

h11@0.14.0 · osv@v1

requirements.txt

PYSEC-2026-348

h11@0.14.0 · osv@v1

requirements.txt

GHSA-65pc-fj4g-8rjx

idna@3.7 · osv@v1

requirements.txt

PYSEC-2026-215

idna@3.7 · osv@v1

requirements.txt

GHSA-cpwx-vrp4-4pq7

jinja2@3.1.4 · osv@v1

requirements.txt

GHSA-gmj6-6f8f-6699

jinja2@3.1.4 · osv@v1

requirements.txt

GHSA-q2x7-8rv6-6q7h

jinja2@3.1.4 · osv@v1

requirements.txt

PYSEC-2026-1471

jinja2@3.1.4 · osv@v1

requirements.txt

PYSEC-2026-1472

jinja2@3.1.4 · osv@v1

requirements.txt

PYSEC-2026-1475

jinja2@3.1.4 · osv@v1

requirements.txt

GHSA-469j-vmhf-r6v7

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-68j8-pq59-fqgm

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-7p94-766c-hgjp

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-cgvx-9447-vcch

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-gfwx-w7gr-fvh7

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-h8wq-7xc4-p3qx

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-jm6w-m3j8-898g

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-p4gq-832x-fm9v

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-rf74-v2fm-23pw

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2024-167

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-2078

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-2085

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-597

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-96

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-97

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-98

nltk@3.8.1 · osv@v1

requirements.txt

PYSEC-2026-99

nltk@3.8.1 · osv@v1

requirements.txt

GHSA-mf9w-mj56-hr94

python-dotenv@1.0.1 · osv@v1

requirements.txt

GHSA-9hjg-9r4m-mvj7

requests@2.32.3 · osv@v1

requirements.txt

GHSA-gc5v-m9x4-r6x2

requests@2.32.3 · osv@v1

requirements.txt

PYSEC-2026-1872

requests@2.32.3 · osv@v1

requirements.txt

GHSA-38vq-g6vr-w8wf

sentencepiece@0.2.0 · osv@v1

requirements.txt

PYSEC-2026-1909

sentencepiece@0.2.0 · osv@v1

requirements.txt

GHSA-3749-ghw9-m3mg

torch@2.3.1 · osv@v1

requirements.txt

GHSA-53q9-r3pm-6pq6

torch@2.3.1 · osv@v1

requirements.txt

GHSA-887c-mr87-cxwp

torch@2.3.1 · osv@v1

requirements.txt

GHSA-c678-jfcj-6jmf

torch@2.3.1 · osv@v1

requirements.txt

GHSA-f4hp-rmr7-r7v8

torch@2.3.1 · osv@v1

requirements.txt

GHSA-qfhq-4f3w-5fph

torch@2.3.1 · osv@v1

requirements.txt

GHSA-rrmf-rvhw-rf47

torch@2.3.1 · osv@v1

requirements.txt

GHSA-vgrw-7cvw-pwgx

torch@2.3.1 · osv@v1

requirements.txt

GHSA-x3gm-94wq-g975

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2024-259

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-191

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-198

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-203

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-204

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-205

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-206

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-207

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-208

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-209

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2025-41

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2026-139

torch@2.3.1 · osv@v1

requirements.txt

PYSEC-2026-1970

torch@2.3.1 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-6rvg-6v2m-4j46

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-fpwr-67px-3qhx

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-hxxf-235m-72v3

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-jjph-296x-mrcr

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-q2wp-rjmx-x6x9

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-qq3j-4f4f-9583

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-qxrp-vhvm-j765

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-wrfc-pvp9-mr9g

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2024-227

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2024-228

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2024-229

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2025-40

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1982

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1984

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1985

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1987

transformers@4.43.1 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.43.1 · osv@v1

requirements.txt

GHSA-2xpw-w6gg-jr37

urllib3@2.2.2 · osv@v1

requirements.txt

GHSA-38jv-5279-wg99

urllib3@2.2.2 · osv@v1

requirements.txt

GHSA-48p4-8xcf-vxj5

urllib3@2.2.2 · osv@v1

requirements.txt

GHSA-gm62-xv2j-4w53

urllib3@2.2.2 · osv@v1

requirements.txt

GHSA-pq67-6m6q-mj2v

urllib3@2.2.2 · osv@v1

requirements.txt

GHSA-qccp-gfcp-xxvc

urllib3@2.2.2 · osv@v1

requirements.txt

PYSEC-2026-141

urllib3@2.2.2 · osv@v1

requirements.txt

PYSEC-2026-1994

urllib3@2.2.2 · osv@v1

requirements.txt

PYSEC-2026-1996

urllib3@2.2.2 · osv@v1

requirements.txt

PYSEC-2026-1997

urllib3@2.2.2 · osv@v1

requirements.txt

PYSEC-2026-1998

urllib3@2.2.2 · osv@v1

requirements.txt

PYSEC-2026-1999

urllib3@2.2.2 · 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/jinjieni-mixeval/trust.

Common questions

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