---
title: "Front-End-Checklist vs tma1"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/thedaviddias-front-end-checklist-vs-tma1-ai-tma1"
tools: ["thedaviddias-front-end-checklist", "tma1-ai-tma1"]
---

# Front-End-Checklist vs tma1

*GraphCanon updated Jul 15, 2026*

## Verdict

Pick Front-End-Checklist when front-End-Checklist is primarily MDX; tma1 is Go; pick tma1 when tma1 is primarily Go; Front-End-Checklist is MDX.

[Front-End-Checklist](https://frontendchecklist.io) reports 73k GitHub stars, 6.7k forks, and 3 open issues, last pushed Jun 18, 2026. [tma1](https://tma1.ai/) has 109 stars, 12 forks, and 5 open issues, last pushed Jul 11, 2026. Figures are from public GitHub metadata via [Front-End-Checklist's repository](https://github.com/thedaviddias/Front-End-Checklist) and [tma1's repository](https://github.com/tma1-ai/tma1).

| | [Front-End-Checklist](/tools/thedaviddias-front-end-checklist.md) | [tma1](/tools/tma1-ai-tma1.md) |
| --- | --- | --- |
| Tagline | The essential checklist for modern web development, for humans and AI agents | Local-first observability your agent reads back. TMA1 records every LLM call, then routes what it sees into the agent's next turn via hooks and MCP. |
| Stars | 73,183 | 109 |
| Forks | 6,650 | 12 |
| Open issues | 3 | 5 |
| Language | MDX | Go |
| Adopt for | Front-End-Checklist is an open-source, comprehensive front-end quality system offering a broad range of best practices and guidelines for web development projects. | - |
| Persona | - | - |
| Runtime | - | - |
| License | - | Apache-2.0 |
| Categories | AI Agents, Developer Tools | AI Agents, Developer Tools, LLM Frameworks |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [Front-End-Checklist](/tools/thedaviddias-front-end-checklist.md) | [tma1](/tools/tma1-ai-tma1.md) |
| --- | --- | --- |
| Maintenance | Active (82%) | Very active (96%) |
| Days since push | 23d | 3d |
| Open issues (now) | 3 | 5 |
| Owner type | User | Organization |
| Full report | [trust report](/tools/thedaviddias-front-end-checklist/trust.md) | [trust report](/tools/tma1-ai-tma1/trust.md) |

## Decision facts: Front-End-Checklist

- **Pricing:** freemium - Free to use as an open-source tool. No specific paid plans are mentioned in the repository.
- **Requirements:** Min 2 GB RAM; - Node.js/pnpm for local development.; - Internet access to use the website or MCP server.
- **Adopt for:** Front-End-Checklist is an open-source, comprehensive front-end quality system offering a broad range of best practices and guidelines for web development projects.

## Choose when

### Choose Front-End-Checklist if…

- Front-End-Checklist is primarily MDX; tma1 is Go.
- Pricing: Free to use as an open-source tool. No specific paid plans are mentioned in the repository..
- Requirements: Min 2 GB RAM; - Node.js/pnpm for local development.; - Internet access to use the website or MCP server..
- Tags unique to Front-End-Checklist: ai-agent, checklist, front-end-development, guidelines.
- - When you need a thorough checklist to ensure high-quality standard across all aspects of your frontend project, including React, Next.js, HTML, CSS, JavaScript, accessibility, performance, SEO, and

### Choose tma1 if…

- tma1 is primarily Go; Front-End-Checklist is MDX.
- Tags unique to tma1: agent-loop, agent-observability, ai-agents, claude code.
- Also covers LLM Frameworks.

## When NOT to use Front-End-Checklist

- - For projects strictly limited to backend development as it focuses on frontend practices and is designed for frontend workflows.
- - In small-scale hobby projects where comprehensive quality reviews might be overkill given the scope of application. Smaller projects may not require such an extensive set of rules and guidelines.
- - If your project already has a well-established, customized checklist that meets all your needs and does not require integration with MCP-capable agents for automated frontend code review.

## When NOT to use tma1

- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
- Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

## Common questions

### What is the difference between Front-End-Checklist and tma1?

Front-End-Checklist: The essential checklist for modern web development, for humans and AI agents. tma1: Local-first observability your agent reads back. TMA1 records every LLM call, then routes what it sees into the agent's next turn via hooks and MCP.. See the comparison table for live GitHub stats and shared categories.

### When should I choose Front-End-Checklist over tma1?

Choose Front-End-Checklist over tma1 when Front-End-Checklist is primarily MDX; tma1 is Go; Pricing: Free to use as an open-source tool. No specific paid plans are mentioned in the repository.; Requirements: Min 2 GB RAM; - Node.js/pnpm for local development.; - Internet access to use the website or MCP server.; Tags unique to Front-End-Checklist: ai-agent, checklist, front-end-development, guidelines; - When you need a thorough checklist to ensure high-quality standard across all aspects of your frontend project, including React, Next.js, HTML, CSS, JavaScript, accessibility, performance, SEO, and.

### When should I choose tma1 over Front-End-Checklist?

Choose tma1 over Front-End-Checklist when tma1 is primarily Go; Front-End-Checklist is MDX; Tags unique to tma1: agent-loop, agent-observability, ai-agents, claude code; Also covers LLM Frameworks.

### When should I avoid Front-End-Checklist?

- For projects strictly limited to backend development as it focuses on frontend practices and is designed for frontend workflows. - In small-scale hobby projects where comprehensive quality reviews might be overkill given the scope of application. Smaller projects may not require such an extensive set of rules and guidelines. - If your project already has a well-established, customized checklist that meets all your needs and does not require integration with MCP-capable agents for automated frontend code review.

### When should I avoid tma1?

AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. Developer Tools: A gateway is overkill when you're pinned to a single provider and model. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.

### Is Front-End-Checklist or tma1 more popular on GitHub?

Front-End-Checklist has more GitHub stars (73,183 vs 109). Stars measure visibility, not whether either tool fits your constraints.

### Are Front-End-Checklist and tma1 open source?

Yes - both are open-source projects on GitHub.

### Where can I find alternatives to Front-End-Checklist or tma1?

GraphCanon lists graph-backed alternatives at [Front-End-Checklist alternatives](/tools/thedaviddias-front-end-checklist/alternatives) and [tma1 alternatives](/tools/tma1-ai-tma1/alternatives) ([Front-End-Checklist markdown twin](/tools/thedaviddias-front-end-checklist/alternatives.md), [tma1 markdown twin](/tools/tma1-ai-tma1/alternatives.md)), ranked by typed relationship edges rather than popularity votes.

### Is there a machine-readable version of this comparison?

Yes. The markdown twin at [this comparison](/compare/thedaviddias-front-end-checklist-vs-tma1-ai-tma1.md) mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.

### Which is better maintained, Front-End-Checklist or tma1?

Front-End-Checklist: Active. tma1: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.

### Where are the full trust reports for Front-End-Checklist and tma1?

GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: [Front-End-Checklist trust report](/tools/thedaviddias-front-end-checklist/trust); [tma1 trust report](/tools/tma1-ai-tma1/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=thedaviddias-front-end-checklist`](/api/graphcanon/graph?tool=thedaviddias-front-end-checklist)
- 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/_
