---
title: "aeneas trust report"
type: "trust-report"
slug: "readbeyond-aeneas"
canonical_url: "https://www.graphcanon.com/tools/readbeyond-aeneas/trust"
computed_at: "2026-07-11T12:08:20.333Z"
maintenance_label: "Dormant"
security_status: "findings"
---

# aeneas 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: Dormant (18% recency signal)
- Days since last push: 749
- Last release: 2017-03-16T12:50:13Z
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 35419406
- Not a fork
- Owner type: User
- Computed at: 2026-07-11T12:08:20.333Z
- Methodology: github_public_v1

## Security scan

- Status: Findings present (0 critical, 0 high, 0 medium, 24 low) · last scan 2026-07-11T12:08:22.711Z

### Findings

- **low**: GHSA-55x5-fj6c-h6m8 (lxml@3.6.0 · requirements.txt)
- **low**: GHSA-jq4v-f5q6-mjqq (lxml@3.6.0 · requirements.txt)
- **low**: GHSA-pgww-xf46-h92r (lxml@3.6.0 · requirements.txt)
- **low**: GHSA-vfmq-68hx-4jfw (lxml@3.6.0 · requirements.txt)
- **low**: GHSA-wrxv-2j5q-m38w (lxml@3.6.0 · requirements.txt)
- **low**: GHSA-xp26-p53h-6h2p (lxml@3.6.0 · requirements.txt)
- **low**: PYSEC-2018-12 (lxml@3.6.0 · requirements.txt)
- **low**: PYSEC-2020-62 (lxml@3.6.0 · requirements.txt)
- **low**: PYSEC-2021-19 (lxml@3.6.0 · requirements.txt)
- **low**: PYSEC-2021-852 (lxml@3.6.0 · requirements.txt)
- **low**: PYSEC-2022-230 (lxml@3.6.0 · requirements.txt)
- **low**: PYSEC-2026-87 (lxml@3.6.0 · requirements.txt)
- **low**: GHSA-5545-2q6w-2gh6 (numpy@1.9 · requirements.txt)
- **low**: GHSA-6p56-wp2h-9hxr (numpy@1.9 · requirements.txt)
- **low**: GHSA-9fq2-x9r6-wfmf (numpy@1.9 · requirements.txt)
- **low**: GHSA-f7c7-j99h-c22f (numpy@1.9 · requirements.txt)
- **low**: GHSA-fpfv-jqm9-f5jm (numpy@1.9 · requirements.txt)
- **low**: GHSA-frgw-fgh6-9g52 (numpy@1.9 · requirements.txt)
- **low**: PYSEC-2017-1 (numpy@1.9 · requirements.txt)
- **low**: PYSEC-2019-108 (numpy@1.9 · requirements.txt)
- **low**: PYSEC-2021-854 (numpy@1.9 · requirements.txt)
- **low**: PYSEC-2021-855 (numpy@1.9 · requirements.txt)
- **low**: PYSEC-2021-856 (numpy@1.9 · requirements.txt)
- **low**: PYSEC-2021-857 (numpy@1.9 · 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 aeneas maintained?

GraphCanon rates aeneas "Dormant" (18% maintenance signal from public GitHub metadata, computed today). Last push was 749 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is aeneas safe to use?

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

### Is aeneas a fork?

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

### Does aeneas have known security vulnerabilities?

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

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

### How does GraphCanon assess trust for aeneas?

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