Trust and health report
llm-workflow-engine - 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.
Steady60% signal
last push 71d ago · last release 2mo · 2 releases (90d)
Provenance
Repository identity and fork provenance (github_public_v1).
- GitHub repo id: 573822937
- Not a fork
- Verified publisher: organization 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-8ggh-xwr9-3373
ansible@8.0 · requirements.txt
GHSA-jpvw-p8pr-9g2x
ansible@8.0 · requirements.txt
PYSEC-2026-1119
ansible@8.0 · requirements.txt
PYSEC-2026-1120
ansible@8.0 · requirements.txt
GHSA-32p4-gm2c-wmch
ansible-core@2.15 · requirements.txt
GHSA-7j69-qfc3-2fq9
ansible-core@2.15 · requirements.txt
GHSA-99w6-3xph-cx78
ansible-core@2.15 · requirements.txt
GHSA-h24r-m9qc-pvpg
ansible-core@2.15 · requirements.txt
GHSA-jpxc-vmjf-9fcj
ansible-core@2.15 · requirements.txt
GHSA-ww3m-ffrm-qvqv
ansible-core@2.15 · requirements.txt
PYSEC-2024-36
ansible-core@2.15 · requirements.txt
PYSEC-2026-1121
ansible-core@2.15 · requirements.txt
PYSEC-2026-1122
ansible-core@2.15 · requirements.txt
PYSEC-2026-1123
ansible-core@2.15 · requirements.txt
PYSEC-2026-1124
ansible-core@2.15 · requirements.txt
PYSEC-2026-1125
ansible-core@2.15 · requirements.txt
GHSA-3644-q5cj-c5c7
langchain@0.3.19 · requirements.txt
GHSA-gr75-jv2w-4656
langchain@0.3.19 · requirements.txt
GHSA-2g6r-c272-w58r
langchain-core@0.3.39 · requirements.txt
GHSA-6qv9-48xg-fc7f
langchain-core@0.3.39 · requirements.txt
GHSA-926x-3r5x-gfhw
langchain-core@0.3.39 · requirements.txt
GHSA-c67j-w6g6-q2cm
langchain-core@0.3.39 · requirements.txt
GHSA-pjwx-r37v-7724
langchain-core@0.3.39 · requirements.txt
GHSA-qh6h-p6c9-ff54
langchain-core@0.3.39 · requirements.txt
PYSEC-2026-1518
langchain-core@0.3.39 · requirements.txt
PYSEC-2026-373
langchain-core@0.3.39 · requirements.txt
GHSA-pc6w-59fv-rh23
langchain-community@0.3.16 · requirements.txt
PYSEC-2026-1515
langchain-community@0.3.16 · requirements.txt
GHSA-r7w7-9xr2-qq2r
langchain_openai@0.3.3 · requirements.txt
PYSEC-2026-76
langchain_openai@0.3.3 · requirements.txt
GHSA-f73w-4m7g-ch9x
numexpr@2.8.4 · requirements.txt
PYSEC-2023-163
numexpr@2.8.4 · 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/llm-workflow-engine-llm-workflow-engine/trust.
Common questions
- Is llm-workflow-engine maintained?
- GraphCanon rates llm-workflow-engine "Steady" (60% maintenance signal from public GitHub metadata, computed today). Last push was 71 days ago. 2 GitHub releases in the last 90 days. This is a recency heuristic, not a guarantee the project will stay maintained.
- Is llm-workflow-engine 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-workflow-engine as safe - review maintenance, provenance, and scan findings on this page before adopting.
- Is llm-workflow-engine a fork?
- No. llm-workflow-engine is not flagged as a fork in GitHub metadata at the time of the last refresh.
- Does llm-workflow-engine 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-workflow-engine 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-workflow-engine?
- We never publish a composite safety grade, pen-test endorsement, or "verified secure" label for llm-workflow-engine. Signals are sourced heuristics with explicit limits - see trust methodology.
- How does GraphCanon assess trust for llm-workflow-engine?
- 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.