Trust and health report
LLMs-from-scratch - 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
52views 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
+2.4k stars (30d) · 0 open issues (30d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 669879380
- Not a fork
- Personal 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
- 46
OpenSSF Scorecard
Not queried- Scanner
- openssf-scorecard@v1
Weekly public scans omit some checks at scale.
View source evidenceDependency advisories (deduplicated)
GHSA-3749-ghw9-m3mg
torch@2.2.2 · osv@v1
requirements.txt
GHSA-53q9-r3pm-6pq6
torch@2.2.2 · osv@v1
requirements.txt
GHSA-887c-mr87-cxwp
torch@2.2.2 · osv@v1
requirements.txt
GHSA-c678-jfcj-6jmf
torch@2.2.2 · osv@v1
requirements.txt
GHSA-f4hp-rmr7-r7v8
torch@2.2.2 · osv@v1
requirements.txt
GHSA-qfhq-4f3w-5fph
torch@2.2.2 · osv@v1
requirements.txt
GHSA-rrmf-rvhw-rf47
torch@2.2.2 · osv@v1
requirements.txt
GHSA-vgrw-7cvw-pwgx
torch@2.2.2 · osv@v1
requirements.txt
GHSA-x3gm-94wq-g975
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2024-259
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-191
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-198
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-203
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-204
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-205
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-206
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-207
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-208
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-209
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2025-41
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2026-139
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2026-1970
torch@2.2.2 · osv@v1
requirements.txt
PYSEC-2026-2286
torch@2.2.2 · osv@v1
requirements.txt
GHSA-37w4-hwhx-4rc4
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-44cc-43rp-5947
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-4m77-cmpx-vjc4
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-9q39-rmj3-p4r2
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-gx64-gj6p-pc4c
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-mqcg-5x36-vfcg
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-pppj-hq3g-57pj
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-rch3-82jr-f9w9
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-vmhf-c436-hxj4
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-vvfj-2jqx-52jm
jupyterlab@4.0 · osv@v1
requirements.txt
GHSA-whvh-wf3x-g77j
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2024-322
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-1482
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-164
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-2534
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-2535
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-2536
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-2537
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-2538
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-3671
jupyterlab@4.0 · osv@v1
requirements.txt
PYSEC-2026-3672
jupyterlab@4.0 · 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
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/rasbt-llms-from-scratch/trust.
Common questions
- Is LLMs-from-scratch maintained?
- GraphCanon rates LLMs-from-scratch "Very active" (96% maintenance signal from public GitHub metadata, computed Sep 18, 2026). Last push was 0 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is LLMs-from-scratch safe to use?
- Last scanned Sep 18, 2026 (deps profile). Status: 46 low - 46 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 LLMs-from-scratch as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is LLMs-from-scratch a fork?
- No. LLMs-from-scratch is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does LLMs-from-scratch have known security vulnerabilities?
- Last scanned Sep 18, 2026 (deps profile). Status: 46 low - 46 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 LLMs-from-scratch 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 LLMs-from-scratch?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for LLMs-from-scratch. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for LLMs-from-scratch?
- 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.