Is clearml maintained?

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

Is clearml safe to use?

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

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

Does clearml have known security vulnerabilities?

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

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

What does GraphCanon never claim about clearml?

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

How does GraphCanon assess trust for clearml?

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

Trust and health report

clearml - trust report

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

GraphCanon updated 2w · GitHub synced 2w

Maintenance

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

Active82% signal

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

Provenance

Repository identity and fork provenance (github_public_v1).

GitHub repo id: 191126383
Not a fork
Verified publisher: organization account
Computed 2w

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

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-6p56-wp2h-9hxr

numpy@1.19.5 · osv@v1

requirements.txt

GHSA-fpfv-jqm9-f5jm

numpy@1.19.5 · osv@v1

requirements.txt

GHSA-3f63-hfp8-52jq

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-3wvg-mj6g-m9cv

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-3xv8-3j54-hgrp

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-43fq-w8qq-v88h

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-44wm-f244-xhp3

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-4fx9-vc88-q2xc

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-57h3-9rgr-c24m

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-7534-mm45-c74v

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-77gc-v2xv-rvvh

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-7r7m-5h27-29hp

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-8843-m7mw-mxqm

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-8ghj-p4vj-mr35

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-8vj2-vxx3-667w

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-8xjq-8fcg-g5hw

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-95q3-8gr9-gm8w

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-98vv-pw6r-q6q4

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-9hx2-hgq2-2g4f

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-9j59-75qj-795w

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-cqhg-xjhh-p8hf

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-f4w8-cv6p-x6r5

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-f5g8-5qq7-938w

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-g6rj-rv7j-xwp4

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-hf64-x4gq-p99h

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-hjfx-8p6c-g7gx

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-j7hp-h8jx-5ppr

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-jgpv-4h4c-xhw3

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-m2vv-5vj5-2hm7

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-mvg9-xffr-p774

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-p43w-g3c5-g5mq

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-pw3c-h7wp-cvhx

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-q5hq-fp76-qmrc

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-r73j-pqj5-w3x7

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-rwv7-3v45-hg29

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-vj42-xq3r-hr3r

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-vqcj-wrf2-7v73

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-wjx4-4jcj-g98j

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-xrcv-f9gm-v42c

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2020-76

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2020-77

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2020-78

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2020-80

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-137

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-138

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-139

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-317

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-331

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-35

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-36

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-37

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-38

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-39

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-40

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-41

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-42

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-69

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-70

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-71

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-92

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-93

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2021-94

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2022-10

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2022-168

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2022-42979

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2022-42980

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2022-8

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2022-9

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2023-175

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2023-227

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2026-165

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2026-1793

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2026-1794

Pillow@7.0.0 · osv@v1

requirements.txt

PYSEC-2026-457

Pillow@7.0.0 · osv@v1

requirements.txt

GHSA-cfh3-3jmp-rvhc

Pillow@10.3.0 · osv@v1

requirements.txt

GHSA-pwv6-vv43-88gr

Pillow@10.3.0 · osv@v1

requirements.txt

GHSA-whj4-6x5x-4v2j

Pillow@10.3.0 · osv@v1

requirements.txt

GHSA-qfc5-mcwq-26q8

psutil@3.4.2 · osv@v1

requirements.txt

PYSEC-2019-41

psutil@3.4.2 · osv@v1

requirements.txt

GHSA-752w-5fwx-jx9f

pyjwt@2.4.0 · osv@v1

requirements.txt

GHSA-993g-76c3-p5m4

pyjwt@2.4.0 · osv@v1

requirements.txt

GHSA-fhv5-28vv-h8m8

pyjwt@2.4.0 · osv@v1

requirements.txt

GHSA-xgmm-8j9v-c9wx

pyjwt@2.4.0 · osv@v1

requirements.txt

PYSEC-2025-183

pyjwt@2.4.0 · osv@v1

requirements.txt

PYSEC-2026-120

pyjwt@2.4.0 · osv@v1

requirements.txt

PYSEC-2026-175

pyjwt@2.4.0 · osv@v1

requirements.txt

PYSEC-2026-177

pyjwt@2.4.0 · osv@v1

requirements.txt

PYSEC-2026-179

pyjwt@2.4.0 · osv@v1

requirements.txt

GHSA-8q59-q68h-6hv4

PyYAML@3.12 · osv@v1

requirements.txt

GHSA-rprw-h62v-c2w7

PyYAML@3.12 · osv@v1

requirements.txt

PYSEC-2018-49

PyYAML@3.12 · osv@v1

requirements.txt

PYSEC-2021-142

PyYAML@3.12 · osv@v1

requirements.txt

GHSA-9hjg-9r4m-mvj7

requests@2.20.0 · osv@v1

requirements.txt

GHSA-9wx4-h78v-vm56

requests@2.20.0 · osv@v1

requirements.txt

GHSA-gc5v-m9x4-r6x2

requests@2.20.0 · osv@v1

requirements.txt

GHSA-j8r2-6x86-q33q

requests@2.20.0 · osv@v1

requirements.txt

PYSEC-2023-74

requests@2.20.0 · osv@v1

requirements.txt

PYSEC-2026-1872

requests@2.20.0 · osv@v1

requirements.txt

PYSEC-2026-1873

requests@2.20.0 · osv@v1

requirements.txt

GHSA-2xpw-w6gg-jr37

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-34jh-p97f-mpxf

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-g4mx-q9vg-27p4

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-gwvm-45gx-3cf8

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-mh33-7rrq-662w

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-pq67-6m6q-mj2v

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-r64q-w8jr-g9qp

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-v845-jxx5-vc9f

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-wqvq-5m8c-6g24

urllib3@1.21.1 · osv@v1

requirements.txt

GHSA-www2-v7xj-xrc6

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2018-32

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2019-132

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2019-133

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2020-148

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2023-192

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2023-207

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2023-212

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2026-1994

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2026-1995

urllib3@1.21.1 · osv@v1

requirements.txt

PYSEC-2026-1999

urllib3@1.21.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/clearml-clearml/trust.

Common questions

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