Trust and health report
llm_agents - 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 382d ago
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 623679404
- Not a fork
- Personal account
- Computed today
Security scan
Dependency advisory security scan when a lockfile is present. Not a full code audit.
- Status
- 32 low
- Last scan
- today
- Scanner
- osv@v1
Findings
GHSA-65pc-fj4g-8rjx
idna@3.10 · poetry.lock
PYSEC-2026-215
idna@3.10 · poetry.lock
GHSA-7gcm-g887-7qv7
protobuf@5.29.5 · poetry.lock
PYSEC-2026-1805
protobuf@5.29.5 · poetry.lock
GHSA-63vm-454h-vhhq
pyasn1@0.6.1 · poetry.lock
GHSA-jr27-m4p2-rc6r
pyasn1@0.6.1 · poetry.lock
PYSEC-2026-1810
pyasn1@0.6.1 · poetry.lock
GHSA-6w46-j5rx-g56g
pytest@7.4.4 · poetry.lock
PYSEC-2026-1845
pytest@7.4.4 · poetry.lock
GHSA-gc5v-m9x4-r6x2
requests@2.32.4 · poetry.lock
GHSA-2wc2-fm75-p42x
soupsieve@2.7 · poetry.lock
GHSA-836r-79rf-4m37
soupsieve@2.7 · poetry.lock
GHSA-2xpw-w6gg-jr37
urllib3@2.2.3 · poetry.lock
GHSA-38jv-5279-wg99
urllib3@2.2.3 · poetry.lock
GHSA-48p4-8xcf-vxj5
urllib3@2.2.3 · poetry.lock
GHSA-gm62-xv2j-4w53
urllib3@2.2.3 · poetry.lock
GHSA-pq67-6m6q-mj2v
urllib3@2.2.3 · poetry.lock
GHSA-qccp-gfcp-xxvc
urllib3@2.2.3 · poetry.lock
PYSEC-2026-141
urllib3@2.2.3 · poetry.lock
PYSEC-2026-1994
urllib3@2.2.3 · poetry.lock
PYSEC-2026-1996
urllib3@2.2.3 · poetry.lock
PYSEC-2026-1997
urllib3@2.2.3 · poetry.lock
PYSEC-2026-1998
urllib3@2.2.3 · poetry.lock
PYSEC-2026-1999
urllib3@2.2.3 · poetry.lock
GHSA-mr82-8j83-vxmv
pydantic@1.10.5 · requirements.txt
PYSEC-2026-1812
pydantic@1.10.5 · requirements.txt
GHSA-9hjg-9r4m-mvj7
requests@2.28.2 · requirements.txt
GHSA-9wx4-h78v-vm56
requests@2.28.2 · requirements.txt
GHSA-j8r2-6x86-q33q
requests@2.28.2 · requirements.txt
PYSEC-2023-74
requests@2.28.2 · requirements.txt
PYSEC-2026-1872
requests@2.28.2 · requirements.txt
PYSEC-2026-1873
requests@2.28.2 · 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/mpaepper-llm-agents/trust.
Common questions
- Is llm_agents maintained?
- GraphCanon rates llm_agents "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 382 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is llm_agents safe to use?
- Last scanned today (deps profile). Status: 32 low - 32 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 llm_agents as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is llm_agents a fork?
- No. llm_agents is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does llm_agents have known security vulnerabilities?
- Last scanned today (deps profile). Status: 32 low - 32 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 llm_agents 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 llm_agents?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for llm_agents. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for llm_agents?
- 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.