Is BizFinBench maintained?

GraphCanon rates BizFinBench "Steady" (60% maintenance signal from public GitHub metadata, computed 4w). Last push was 88 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

Is BizFinBench safe to use?

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

Is BizFinBench a fork?

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

Does BizFinBench have known security vulnerabilities?

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

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

What does GraphCanon never claim about BizFinBench?

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

How does GraphCanon assess trust for BizFinBench?

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

Trust and health report

BizFinBench - trust report

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

GraphCanon updated 4w · GitHub synced 4w · 27 views this month

Maintenance

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

Steady60% signal

last push 88d ago

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 979225416
Not a fork
Verified publisher: organization account
Computed 4w

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

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-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-27jp-wm6q-gp25

sqlparse@0.5.1 · osv@v1

requirements.txt

GHSA-3f6c-7fw2-ppm4

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-3mwp-wvh9-7528

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-3ww4-5jv9-j5gm

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-4qjh-9fv9-r85r

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-4r2x-xpjr-7cvv

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-5jv2-g5wq-cmr4

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-69j4-grxj-j64p

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-6fvq-23cw-5628

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-6pr9-rp53-2pmc

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-6qc9-v4r8-22xg

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-7h4p-rffg-7823

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-8fr4-5q9j-m8gm

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-94f4-hr76-p5j6

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-98f3-hwg4-4rf7

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-9hcf-v7m4-6m2j

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-9pcc-gvx5-r5wm

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-c65p-x677-fgj6

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-grg2-63fw-f2qr

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-hgg8-fqqc-vfmw

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-hpv8-x276-m59f

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-j828-28rj-hfhp

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-pmqf-x6x8-p7qw

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-pq5c-rjhq-qp7p

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-q8gq-377p-jq3r

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-qh4c-xf7m-gxfc

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-rxc4-3w6r-4v47

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-vrq3-r879-7m65

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-w6q7-j642-7c25

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-wr9h-g72x-mwhm

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-x368-4g9h-fvv4

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2025-43

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2025-50

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2025-53

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2025-54

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2025-55

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-143

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-144

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2011

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2012

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2013

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2015

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2017

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2019

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2020

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2021

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2023

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-2026

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-226

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-227

vllm@0.8.5 · osv@v1

requirements.txt

PYSEC-2026-565

vllm@0.8.5 · osv@v1

requirements.txt

GHSA-29pf-2h5f-8g72

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-37mw-44qp-f5jm

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-4w7r-h757-3r74

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-59p9-h35m-wg4g

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-69w3-r845-3855

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-9356-575x-2w9m

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-phhr-52qp-3mj4

transformers@4.51.0 · osv@v1

requirements.txt

GHSA-rcv9-qm8p-9p6j

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-211

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-212

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-213

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-214

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-215

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-216

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-217

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2025-218

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2026-1977

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2026-1980

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2026-1981

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2026-1983

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2026-1986

transformers@4.51.0 · osv@v1

requirements.txt

PYSEC-2026-1988

transformers@4.51.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-bizfinbench/trust.

Common questions

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