Trust and health report
JOOD - 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 · 27 views this month
Maintenance
Recency and activity heuristics from public GitHub metadata (maintenance label, momentum); methodology: github_public_v1.
Dormant18% signal
last push 419d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 949698747
- 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
- 50
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-5xmw-vc9v-4wf2
Pillow@11.2.1 · osv@v1
requirements.txt
GHSA-cfh3-3jmp-rvhc
Pillow@11.2.1 · osv@v1
requirements.txt
GHSA-pwv6-vv43-88gr
Pillow@11.2.1 · osv@v1
requirements.txt
GHSA-r73j-pqj5-w3x7
Pillow@11.2.1 · osv@v1
requirements.txt
GHSA-whj4-6x5x-4v2j
Pillow@11.2.1 · osv@v1
requirements.txt
GHSA-wjx4-4jcj-g98j
Pillow@11.2.1 · osv@v1
requirements.txt
GHSA-xg8h-j46f-w952
Pillow@11.2.1 · osv@v1
requirements.txt
PYSEC-2025-61
Pillow@11.2.1 · osv@v1
requirements.txt
PYSEC-2026-165
Pillow@11.2.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-3749-ghw9-m3mg
torch@2.7.0 · osv@v1
requirements.txt
GHSA-887c-mr87-cxwp
torch@2.7.0 · osv@v1
requirements.txt
GHSA-qfhq-4f3w-5fph
torch@2.7.0 · osv@v1
requirements.txt
GHSA-rrmf-rvhw-rf47
torch@2.7.0 · osv@v1
requirements.txt
GHSA-vgrw-7cvw-pwgx
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-203
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-204
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-205
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-206
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-207
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-208
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2025-209
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2026-139
torch@2.7.0 · osv@v1
requirements.txt
PYSEC-2026-1970
torch@2.7.0 · osv@v1
requirements.txt
GHSA-29pf-2h5f-8g72
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-37mw-44qp-f5jm
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-4w7r-h757-3r74
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-59p9-h35m-wg4g
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-69w3-r845-3855
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-9356-575x-2w9m
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-phhr-52qp-3mj4
transformers@4.51.3 · osv@v1
requirements.txt
GHSA-rcv9-qm8p-9p6j
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-211
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-212
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-213
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-214
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-215
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-216
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-217
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2025-218
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2026-1977
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2026-1980
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2026-1981
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2026-1983
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2026-1986
transformers@4.51.3 · osv@v1
requirements.txt
PYSEC-2026-1988
transformers@4.51.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
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/naver-ai-jood/trust.
Common questions
- Is JOOD maintained?
- GraphCanon rates JOOD "Dormant" (18% maintenance signal from public GitHub metadata, computed 2w). Last push was 419 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is JOOD safe to use?
- Last scanned 1mo (deps profile). Status: 50 low - 50 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 JOOD as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is JOOD a fork?
- No. JOOD is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does JOOD have known security vulnerabilities?
- Last scanned 1mo (deps profile). Status: 50 low - 50 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 JOOD 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 JOOD?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for JOOD. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for JOOD?
- 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.