Is great_expectations maintained?

GraphCanon rates great_expectations "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 0 days ago. 7 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.

Is great_expectations safe to use?

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

Is great_expectations a fork?

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

Does great_expectations have known security vulnerabilities?

Last scanned Sep 18, 2026 (deps profile). Status: 78 low - 78 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 great_expectations trust report updated?

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

What does GraphCanon never claim about great_expectations?

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

How does GraphCanon assess trust for great_expectations?

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

Trust and health report

great_expectations - trust report

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

GraphCanon updated Sep 20, 2026 · GitHub synced Sep 20, 2026

31views this month

Maintenance

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

Very active96% signal

last push 0d ago · last release Sep 10, 2026 · 7 releases (90d)

+108 stars (30d) · +8 open issues (30d)

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 103071520
Not a fork
Verified publisher: organization account
Computed Sep 18, 2026

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: Sep 18, 2026
Scanner: osv@v1
Stored findings: 78

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-3ww4-gg4f-jr7f

cryptography@3.2 · osv@v1

requirements.txt

GHSA-537c-gmf6-5ccf

cryptography@3.2 · osv@v1

requirements.txt

GHSA-5cpq-8wj7-hf2v

cryptography@3.2 · osv@v1

requirements.txt

GHSA-9v9h-cgj8-h64p

cryptography@3.2 · osv@v1

requirements.txt

GHSA-jfhm-5ghh-2f97

cryptography@3.2 · osv@v1

requirements.txt

GHSA-jm77-qphf-c4w8

cryptography@3.2 · osv@v1

requirements.txt

GHSA-m959-cc7f-wv43

cryptography@3.2 · osv@v1

requirements.txt

GHSA-r6ph-v2qm-q3c2

cryptography@3.2 · osv@v1

requirements.txt

GHSA-rhm9-p9w5-fwm7

cryptography@3.2 · osv@v1

requirements.txt

GHSA-v8gr-m533-ghj9

cryptography@3.2 · osv@v1

requirements.txt

GHSA-w7pp-m8wf-vj6r

cryptography@3.2 · osv@v1

requirements.txt

GHSA-x4qr-2fvf-3mr5

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2021-62

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2021-63

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2023-11

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2023-254

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2024-225

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-1283

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-1285

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-2141

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-35

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-3553

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-3554

cryptography@3.2 · osv@v1

requirements.txt

PYSEC-2026-800

cryptography@3.2 · osv@v1

requirements.txt

GHSA-cpwx-vrp4-4pq7

jinja2@3 · osv@v1

requirements.txt

GHSA-gmj6-6f8f-6699

jinja2@3 · osv@v1

requirements.txt

GHSA-h5c8-rqwp-cp95

jinja2@3 · osv@v1

requirements.txt

GHSA-h75v-3vvj-5mfj

jinja2@3 · osv@v1

requirements.txt

GHSA-q2x7-8rv6-6q7h

jinja2@3 · osv@v1

requirements.txt

PYSEC-2026-1471

jinja2@3 · osv@v1

requirements.txt

PYSEC-2026-1472

jinja2@3 · osv@v1

requirements.txt

PYSEC-2026-1473

jinja2@3 · osv@v1

requirements.txt

PYSEC-2026-1474

jinja2@3 · osv@v1

requirements.txt

PYSEC-2026-1475

jinja2@3 · osv@v1

requirements.txt

GHSA-428g-f7cq-pgp5

marshmallow@3.18.0 · osv@v1

requirements.txt

PYSEC-2026-1605

marshmallow@3.18.0 · osv@v1

requirements.txt

GHSA-2hm2-hc3v-44h9

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-4j32-57v6-6g45

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-58cw-g322-p94v

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-8c25-4j27-2rv3

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-8g87-j6q8-g93x

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-8mpj-m6qm-5qr8

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-c8j7-8cv4-2xmq

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-ffq3-xpv3-j92q

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-g97x-gvcm-x72h

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-qcq2-496w-v96p

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-qfrw-5rxm-mhh2

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-r4rv-85jg-w4mf

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-v87v-83h2-53w7

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-168

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2206

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2207

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2208

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2209

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2210

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2211

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2212

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2213

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2214

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2215

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2216

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2217

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2218

mistune@0.8.4 · osv@v1

requirements.txt

PYSEC-2026-2652

mistune@0.8.4 · osv@v1

requirements.txt

GHSA-mr82-8j83-vxmv

pydantic@1.10.7 · osv@v1

requirements.txt

PYSEC-2026-1812

pydantic@1.10.7 · osv@v1

requirements.txt

GHSA-9hjg-9r4m-mvj7

requests@2.20 · osv@v1

requirements.txt

GHSA-9wx4-h78v-vm56

requests@2.20 · osv@v1

requirements.txt

GHSA-gc5v-m9x4-r6x2

requests@2.20 · osv@v1

requirements.txt

GHSA-j8r2-6x86-q33q

requests@2.20 · osv@v1

requirements.txt

PYSEC-2023-74

requests@2.20 · osv@v1

requirements.txt

PYSEC-2026-1872

requests@2.20 · osv@v1

requirements.txt

PYSEC-2026-1873

requests@2.20 · osv@v1

requirements.txt

PYSEC-2026-2275

requests@2.20 · osv@v1

requirements.txt

PYSEC-2023-102

scipy@1.6.0 · osv@v1

requirements.txt

PYSEC-2023-114

scipy@1.6.0 · osv@v1

requirements.txt

GHSA-g7vv-2v7x-gj9p

tqdm@4.59.0 · osv@v1

requirements.txt

PYSEC-2026-1976

tqdm@4.59.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/fivetran-great-expectations/trust.

Common questions

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