GraphCanon
Home/mengram/Trust report

Trust and health report

mengram - trust report

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

GraphCanon updated today · GitHub synced today

Maintenance

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

Active82% signal

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

Provenance

Repository identity and fork provenance (github_public_v1).

  • GitHub repo id: 1154785536
  • Not a fork
  • Personal account
  • Computed today

Security scan

Dependency advisory security scan when a lockfile is present. Not a full code audit.

Status
23 low
Last scan
today
Scanner
osv@v1

Findings

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

Method and caveats:these are sourced, dated heuristics from public GitHub data and optional dependency scans. A status like "no criticals found on 2026-07-11" is not a guarantee of safety. Read the full trust methodology · JSON report at /api/graphcanon/tools/alibaizhanov-mengram/trust.

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.
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 for full scope and limits.