---
title: "MOE trust report"
type: "trust-report"
slug: "yelparchive-moe"
canonical_url: "https://www.graphcanon.com/tools/yelparchive-moe/trust"
computed_at: "2026-07-11T23:35:49.399Z"
maintenance_label: "Archived"
security_status: "findings"
---

# MOE trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and optional dependency [security scans](/glossary/trust-and-signals/security-scan). Not a security guarantee._

## Maintenance

- Label: Archived (8% recency signal)
- Days since last push: 1205
- Last release: 2014-12-05T22:58:52Z
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 17152267
- Not a fork
- Owner type: Organization
- Computed at: 2026-07-11T23:35:49.399Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 15 low) · last scan 2026-07-11T23:35:49.913Z

### Findings

- **low**: GHSA-6w46-j5rx-g56g (pytest@2.6.3 · requirements.txt)
- **low**: PYSEC-2026-1845 (pytest@2.6.3 · requirements.txt)
- **low**: GHSA-5545-2q6w-2gh6 (numpy@1.8.1 · requirements.txt)
- **low**: GHSA-9fq2-x9r6-wfmf (numpy@1.8.1 · requirements.txt)
- **low**: GHSA-f7c7-j99h-c22f (numpy@1.8.1 · requirements.txt)
- **low**: GHSA-fpfv-jqm9-f5jm (numpy@1.8.1 · requirements.txt)
- **low**: GHSA-frgw-fgh6-9g52 (numpy@1.8.1 · requirements.txt)
- **low**: PYSEC-2017-1 (numpy@1.8.1 · requirements.txt)
- **low**: PYSEC-2019-108 (numpy@1.8.1 · requirements.txt)
- **low**: PYSEC-2021-856 (numpy@1.8.1 · requirements.txt)
- **low**: PYSEC-2021-857 (numpy@1.8.1 · requirements.txt)
- **low**: PYSEC-2023-102 (scipy@0.14.0 · requirements.txt)
- **low**: PYSEC-2023-114 (scipy@0.14.0 · requirements.txt)
- **low**: GHSA-rv95-4wxj-6fqq (colander@1.0b1 · requirements.txt)
- **low**: PYSEC-2019-167 (colander@1.0b1 · requirements.txt)

## Method and caveats

These are heuristics from public GitHub data and optional dependency scans, sourced and dated. 
"No criticals found on 2026-07-11" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is MOE maintained?

MOE is archived on GitHub. GraphCanon treats archived repositories as dormant regardless of past activity.

### Is MOE safe to use?

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

### Is MOE a fork?

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

### Does MOE have known security vulnerabilities?

Last scanned today (deps profile). Status: 15 low - 15 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 MOE trust report updated?

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

### What does GraphCanon never claim about MOE?

We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for MOE. Signals are sourced heuristics with explicit limits - see [trust methodology](/trust-methodology).

### How does GraphCanon assess trust for MOE?

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](/trust-methodology) for full scope and limits.

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/tools/yelparchive-moe/trust`](/api/graphcanon/tools/yelparchive-moe/trust)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_