---
title: "mengram trust report"
type: "trust-report"
slug: "alibaizhanov-mengram"
canonical_url: "https://www.graphcanon.com/tools/alibaizhanov-mengram/trust"
computed_at: "2026-07-11T23:17:11.391Z"
maintenance_label: "Active"
security_status: "findings"
---

# mengram 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: Active (82% recency signal)
- Days since last push: 24
- Last release: 2026-05-14T12:23:24Z
- Releases (90d): 1
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 1154785536
- Not a fork
- Owner type: User
- Computed at: 2026-07-11T23:17:11.391Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 23 low) · last scan 2026-07-11T23:17:11.881Z

### Findings

- **low**: PYSEC-2024-38 (fastapi@0.100 · requirements.txt)
- **low**: GHSA-hc5x-x2vx-497g (gunicorn@21.0 · requirements.txt)
- **low**: GHSA-w3h3-4rj7-4ph4 (gunicorn@21.0 · requirements.txt)
- **low**: PYSEC-2026-1433 (gunicorn@21.0 · requirements.txt)
- **low**: PYSEC-2026-1434 (gunicorn@21.0 · requirements.txt)
- **low**: GHSA-2jv5-9r88-3w3p (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-59g5-xgcq-4qw3 (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-5rvq-cxj2-64vf (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-6jv3-5f52-599m (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-mj87-hwqh-73pj (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-pp6c-gr5w-3c5g (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-v9pg-7xvm-68hf (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-vffw-93wf-4j4q (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-wp53-j4wj-2cfg (python-multipart@0.0.6 · requirements.txt)
- **low**: PYSEC-2026-1850 (python-multipart@0.0.6 · requirements.txt)
- **low**: PYSEC-2026-1851 (python-multipart@0.0.6 · requirements.txt)
- **low**: PYSEC-2026-1852 (python-multipart@0.0.6 · requirements.txt)
- **low**: GHSA-3qhf-m339-9g5v (mcp@1.0 · requirements.txt)
- **low**: GHSA-9h52-p55h-vw2f (mcp@1.0 · requirements.txt)
- **low**: GHSA-j975-95f5-7wqh (mcp@1.0 · requirements.txt)
- **low**: PYSEC-2026-1616 (mcp@1.0 · requirements.txt)
- **low**: PYSEC-2026-1617 (mcp@1.0 · requirements.txt)
- **low**: PYSEC-2026-1618 (mcp@1.0 · 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 mengram maintained?

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

### Is mengram safe to use?

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

### Is mengram a fork?

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

### Does mengram have known security vulnerabilities?

Last scanned today (deps profile). Status: 23 low - 23 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 mengram 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 mengram?

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

### How does GraphCanon assess trust for mengram?

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/alibaizhanov-mengram/trust`](/api/graphcanon/tools/alibaizhanov-mengram/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/_