---
title: "llm-axe trust report"
type: "trust-report"
slug: "emirsahin1-llm-axe"
canonical_url: "https://www.graphcanon.com/tools/emirsahin1-llm-axe/trust"
computed_at: "2026-07-15T11:00:04.801Z"
maintenance_label: "Dormant"
security_status: "no_lockfile"
---

# llm-axe trust report

_Sourced [trust signals](/glossary/trust-and-signals/trust-signal) from public GitHub metadata and external security intelligence providers. Not a security guarantee._

## Maintenance

- Label: Dormant (18% recency signal)
- Days since last push: 555
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 790018635
- Not a fork
- Owner type: User
- Computed at: 2026-07-15T11:00:04.801Z
- Methodology: github_public_v1

## Security intelligence

- **OSV dependency advisories**: No lockfile (source not queried)
  - Last query: 2026-07-15T11:00:05.718868+00:00
  - Evidence: https://osv.dev/
- **deps.dev advisories**: Not queried
  - Evidence: https://deps.dev/
- **OpenSSF Scorecard**: Not queried
  - Evidence: https://api.securityscorecards.dev/projects/github.com/emirsahin1/llm-axe
  - Note: Weekly public scans omit some checks at scale.

## Method and caveats

These are heuristics from public GitHub data and external security intelligence providers, sourced and dated. 
"No published findings from this source" is not a guarantee of safety.
See the full methodology: [/trust-methodology](/trust-methodology.md).

## Common questions

### Is llm-axe maintained?

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

### Is llm-axe safe to use?

Last scanned today (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits. GraphCanon does not certify llm-axe as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is llm-axe a fork?

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

### Does llm-axe have known security vulnerabilities?

Last scanned today (none profile). Status: No lockfile. Absence of findings in our scan is not a security guarantee - see [trust methodology](/trust-methodology) for scope limits.

### How often is the llm-axe 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-axe?

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

### How does GraphCanon assess trust for llm-axe?

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/emirsahin1-llm-axe/trust`](/api/graphcanon/tools/emirsahin1-llm-axe/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/_