---
title: "awesome-llm-human-preference-datasets trust report"
type: "trust-report"
slug: "glgh-awesome-llm-human-preference-datasets"
canonical_url: "https://www.graphcanon.com/tools/glgh-awesome-llm-human-preference-datasets/trust"
computed_at: "2026-07-11T10:32:10.353Z"
maintenance_label: "Dormant"
security_status: "no_lockfile"
---

# awesome-llm-human-preference-datasets 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: 1010
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 635880783
- Not a fork
- Owner type: User
- Computed at: 2026-07-11T10:32:10.353Z
- Methodology: github_public_v1

## Security scan

- Status: No lockfile (0 critical, 0 high, 0 medium, 0 low) · last scan 2026-07-11T10:32:11.326Z

## 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 awesome-llm-human-preference-datasets maintained?

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

### Is awesome-llm-human-preference-datasets 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 awesome-llm-human-preference-datasets as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is awesome-llm-human-preference-datasets a fork?

No. awesome-llm-human-preference-datasets is not flagged as a fork in GitHub metadata at the time of the last refresh.

### Does awesome-llm-human-preference-datasets 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 awesome-llm-human-preference-datasets 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 awesome-llm-human-preference-datasets?

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

### How does GraphCanon assess trust for awesome-llm-human-preference-datasets?

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/glgh-awesome-llm-human-preference-datasets/trust`](/api/graphcanon/tools/glgh-awesome-llm-human-preference-datasets/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/_