GraphCanon
Home/CivAgent/Trust report

Trust and health report

CivAgent - 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.

Dormant18% signal

last push 481d ago

Provenance

Repository identity and fork provenance (github_public_v1).

Security scan

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

Status
43 low
Last scan
today
Scanner
osv@v1

Findings

GHSA-68rp-wp8r-4726
Flask@2.0.3 · requirements.txt
GHSA-m2qf-hxjv-5gpq
Flask@2.0.3 · requirements.txt
PYSEC-2023-62
Flask@2.0.3 · requirements.txt
GHSA-9hjg-9r4m-mvj7
Requests@2.32.3 · requirements.txt
GHSA-gc5v-m9x4-r6x2
Requests@2.32.3 · requirements.txt
PYSEC-2026-1872
Requests@2.32.3 · requirements.txt
GHSA-29vq-49wr-vm6x
Werkzeug@2.0.3 · requirements.txt
GHSA-2g68-c3qc-8985
Werkzeug@2.0.3 · requirements.txt
GHSA-87hc-h4r5-73f7
Werkzeug@2.0.3 · requirements.txt
GHSA-f9vj-2wh5-fj8j
Werkzeug@2.0.3 · requirements.txt
GHSA-hgf8-39gv-g3f2
Werkzeug@2.0.3 · requirements.txt
GHSA-hrfv-mqp8-q5rw
Werkzeug@2.0.3 · requirements.txt
GHSA-px8h-6qxv-m22q
Werkzeug@2.0.3 · requirements.txt
GHSA-q34m-jh98-gwm2
Werkzeug@2.0.3 · requirements.txt
GHSA-xg9f-g7g7-2323
Werkzeug@2.0.3 · requirements.txt
PYSEC-2022-203
Werkzeug@2.0.3 · requirements.txt
PYSEC-2023-221
Werkzeug@2.0.3 · requirements.txt
PYSEC-2023-57
Werkzeug@2.0.3 · requirements.txt
PYSEC-2023-58
Werkzeug@2.0.3 · requirements.txt
PYSEC-2026-2043
Werkzeug@2.0.3 · requirements.txt
PYSEC-2026-2044
Werkzeug@2.0.3 · requirements.txt
PYSEC-2026-2045
Werkzeug@2.0.3 · requirements.txt
PYSEC-2026-2046
Werkzeug@2.0.3 · requirements.txt
GHSA-3j69-69wj-xqx2
ujson@5.10.0 · requirements.txt
GHSA-c38f-wx89-p2xg
ujson@5.10.0 · requirements.txt
GHSA-c8rr-9gxc-jprv
ujson@5.10.0 · requirements.txt
GHSA-wgvc-ghv9-3pmm
ujson@5.10.0 · requirements.txt
GHSA-5hq9-5r78-2gjh
llama_index@0.10.58 · requirements.txt
GHSA-jmgm-gx32-vp4w
llama_index@0.10.58 · requirements.txt
GHSA-jvpf-xf32-2w4q
llama_index@0.10.58 · requirements.txt
GHSA-rg9h-vx28-xxp5
llama_index@0.10.58 · requirements.txt
GHSA-v3c8-3pr6-gr7p
llama_index@0.10.58 · requirements.txt
PYSEC-2025-11
llama_index@0.10.58 · requirements.txt
PYSEC-2026-1555
llama_index@0.10.58 · requirements.txt
PYSEC-2026-1556
llama_index@0.10.58 · requirements.txt
PYSEC-2026-394
llama_index@0.10.58 · requirements.txt
PYSEC-2026-85
llama_index@0.10.58 · requirements.txt
PYSEC-2026-86
llama_index@0.10.58 · requirements.txt
GHSA-6w46-j5rx-g56g
pytest@7.4.3 · requirements.txt
PYSEC-2026-1845
pytest@7.4.3 · requirements.txt
GHSA-3936-cmfr-pm3m
black@23.11.0 · requirements.txt
GHSA-fj7x-q9j7-g6q6
black@23.11.0 · requirements.txt
PYSEC-2024-48
black@23.11.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/fuxiailab-civagent/trust.

Common questions

Is CivAgent maintained?
GraphCanon rates CivAgent "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 481 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
Is CivAgent safe to use?
Last scanned today (deps profile). Status: 43 low - 43 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 CivAgent as safe - review maintenance, provenance, and scan findings on this page before adopting.
Is CivAgent a fork?
No. CivAgent is not flagged as a fork in GitHub metadata at the time of the last refresh.
Does CivAgent have known security vulnerabilities?
Last scanned today (deps profile). Status: 43 low - 43 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 CivAgent 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 CivAgent?
We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for CivAgent. Signals are sourced heuristics with explicit limits - see trust methodology.
How does GraphCanon assess trust for CivAgent?
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.