Is FinRobot maintained?

GraphCanon rates FinRobot "Active" (82% maintenance signal from public GitHub metadata, computed 1d). Last push was 21 days ago. 1 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Is FinRobot safe to use?

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

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

Does FinRobot have known security vulnerabilities?

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

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

What does GraphCanon never claim about FinRobot?

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

How does GraphCanon assess trust for FinRobot?

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

Trust and health report

FinRobot - trust report

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

GraphCanon updated 1d · GitHub synced 1d

Maintenance

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

Active82% signal

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

+214 stars (30d) · +1 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 763842651
Not a fork
Verified publisher: organization account
Computed 1d

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

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-5rjg-fvgr-3xxf

setuptools@41.4.0 · osv@v1

requirements.txt

GHSA-cx63-2mw6-8hw5

setuptools@41.4.0 · osv@v1

requirements.txt

GHSA-r9hx-vwmv-q579

setuptools@41.4.0 · osv@v1

requirements.txt

PYSEC-2022-43012

setuptools@41.4.0 · osv@v1

requirements.txt

PYSEC-2025-49

setuptools@41.4.0 · osv@v1

requirements.txt

PYSEC-2026-1918

setuptools@41.4.0 · osv@v1

requirements.txt

GHSA-qwmp-2cf2-g9g6

wheel@0.33.6 · osv@v1

requirements.txt

PYSEC-2022-43017

wheel@0.33.6 · osv@v1

requirements.txt

GHSA-9g3x-6x24-vf9f

pdfkit@1.0.0 · osv@v1

requirements.txt

GHSA-2fqr-mr3j-6wp8

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-2vrm-gr82-f7m5

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-3wq7-rqq7-wx6j

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-4fvr-rgm6-gqmc

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-4m7w-qmgq-4wj5

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-54jq-c3m8-4m76

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-5h86-8mv2-jq9f

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-5m98-qgg9-wh84

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-63hf-3vf5-4wqf

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-63hw-fmq6-xxg2

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-69f9-5gxw-wvc2

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-6jhg-hg63-jvvf

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-6mq8-rvhq-8wgg

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-7gpw-8wmc-pm8g

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-8495-4g3g-x7pr

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-8qpw-xqxj-h4r2

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-9548-qrrj-x5pj

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-966j-vmvw-g2g9

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-9x8q-7h8h-wcw9

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-c427-h43c-vf67

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-fh55-r93g-j68g

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-g3cq-j2xw-wf74

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-g84x-mcqj-x9qq

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-gfw2-4jvh-wgfg

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-hcc4-c3v8-rx92

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-hg6j-4rv6-33pg

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-hpj7-wq8m-9hgp

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-jg22-mg44-37j8

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-jj3x-wxrx-4x23

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-m5qp-6w8w-w647

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-m6qw-4cw2-hm4m

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-mqqc-3gqh-h2x8

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-mwh4-6h8g-pg8w

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-p998-jp59-783m

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-pjjw-qhg8-p2p9

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-q3qx-c6g2-7pw2

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-qvrw-v9rv-5rjx

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-w2fm-2cpv-w7v5

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-xcgm-r5h9-7989

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2023-246

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2023-250

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2023-251

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2024-24

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2024-26

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1097

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1098

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1099

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1100

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1101

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1102

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1103

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1104

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1105

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1106

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1107

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-1109

aiohttp@3.8.5 · osv@v1

requirements.txt

PYSEC-2026-237

aiohttp@3.8.5 · osv@v1

requirements.txt

GHSA-3644-q5cj-c5c7

langchain@0.1.20 · osv@v1

requirements.txt

GHSA-3hjh-jh2h-vrg6

langchain@0.1.20 · osv@v1

requirements.txt

GHSA-45pg-36p6-83v9

langchain@0.1.20 · osv@v1

requirements.txt

GHSA-gr75-jv2w-4656

langchain@0.1.20 · osv@v1

requirements.txt

PYSEC-2024-118

langchain@0.1.20 · osv@v1

requirements.txt

PYSEC-2026-1507

langchain@0.1.20 · 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-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

GHSA-2c2j-9gv5-cj73

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-82w8-qh3p-5jfq

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-86qp-5c8j-p5mr

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-f96h-pmfr-66vw

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-jp82-jpqv-5vv3

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-wqp7-x3pw-xc5r

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-x746-7m8f-x49c

starlette@0.37.2 · osv@v1

requirements.txt

PYSEC-2026-161

starlette@0.37.2 · osv@v1

requirements.txt

PYSEC-2026-1941

starlette@0.37.2 · osv@v1

requirements.txt

PYSEC-2026-1943

starlette@0.37.2 · osv@v1

requirements.txt

PYSEC-2026-248

starlette@0.37.2 · osv@v1

requirements.txt

PYSEC-2026-249

starlette@0.37.2 · osv@v1

requirements.txt

GHSA-g7vv-2v7x-gj9p

tqdm@4.66.1 · osv@v1

requirements.txt

PYSEC-2026-1976

tqdm@4.66.1 · osv@v1

requirements.txt

GHSA-32r8-54hf-c9p3

unstructured@0.8.1 · osv@v1

requirements.txt

GHSA-gm8q-m8mv-jj5m

unstructured@0.8.1 · osv@v1

requirements.txt

PYSEC-2026-1993

unstructured@0.8.1 · osv@v1

requirements.txt

PYSEC-2026-558

unstructured@0.8.1 · 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/ai4finance-foundation-finrobot/trust.

Common questions

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