---
title: "finetuning-scheduler trust report"
type: "trust-report"
slug: "speediedan-finetuning-scheduler"
canonical_url: "https://www.graphcanon.com/tools/speediedan-finetuning-scheduler/trust"
computed_at: "2026-07-11T23:22:05.665Z"
maintenance_label: "Slowing"
security_status: "no_lockfile"
---

# finetuning-scheduler 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: Slowing (36% recency signal)
- Days since last push: 166
- Last release: 2026-01-26T17:55:56Z
- Methodology: github_public_v1

## Provenance

- GitHub repo id: 455666112
- Not a fork
- Owner type: User
- Computed at: 2026-07-11T23:22:05.665Z
- Methodology: github_public_v1

## Security scan

- Status: No lockfile (0 critical, 0 high, 0 medium, 0 low) · last scan 2026-07-11T23:22:06.203Z

## 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 finetuning-scheduler maintained?

GraphCanon rates finetuning-scheduler "Slowing" (36% maintenance signal from public GitHub metadata, computed today). Last push was 166 days ago. This is a recency heuristic, not a guarantee the project will stay maintained.

### Is finetuning-scheduler 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 finetuning-scheduler as safe - review maintenance, provenance, and scan findings on this page before adopting.

### Is finetuning-scheduler a fork?

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

### Does finetuning-scheduler 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 finetuning-scheduler 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 finetuning-scheduler?

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

### How does GraphCanon assess trust for finetuning-scheduler?

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/speediedan-finetuning-scheduler/trust`](/api/graphcanon/tools/speediedan-finetuning-scheduler/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/_