Comparison
dust vs Front-End-Checklist
Verdict
Pick dust when dust is primarily TypeScript; Front-End-Checklist is MDX; pick Front-End-Checklist when front-End-Checklist is primarily MDX; dust is TypeScript.
Markdown twin · dust alternatives · Front-End-Checklist alternatives
GraphCanon updated today
vs
Trust & integrity
| Signal | dust | Front-End-Checklist |
|---|---|---|
| Maintenance | Very active (0d since push) As of today · github_public_v1 | Active (23d since push) As of today · github_public_v1 |
| Provenance | Not a fork · Organization account As of today · github_public_v1 | Not a fork · Personal account As of today · github_public_v1 |
| Security (OSV) | No lockfile As of today · none | No lockfile As of today · none |
Tagline
- dust
- Custom AI agent platform to speed up your work.
- Front-End-Checklist
- The essential checklist for modern web development, for humans and AI agents
Stars
- dust
- 1.4k
- Front-End-Checklist
- 73k
Forks
- dust
- 302
- Front-End-Checklist
- 6.7k
Open issues
- dust
- 224
- Front-End-Checklist
- 3
Language
- dust
- TypeScript
- Front-End-Checklist
- MDX
Adopt for
- dust
- -
- Front-End-Checklist
- 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
- dust
- -
- Front-End-Checklist
- -
Runtime
- dust
- -
- Front-End-Checklist
- -
License
- dust
- MIT
- Front-End-Checklist
- -
Last pushed
- dust
- Jul 11, 2026
- Front-End-Checklist
- Jun 18, 2026
Categories
- dust
- AI Agents, LLM Frameworks, Developer Tools
- Front-End-Checklist
- AI Agents, Developer Tools
Trust and health
Maintenance
- dust
- Very active (96%)
- Front-End-Checklist
- Active (82%)
Days since push
- dust
- 0d
- Front-End-Checklist
- 23d
Open issues (now)
- dust
- 224
- Front-End-Checklist
- 3
Owner type
- dust
- Organization
- Front-End-Checklist
- User
Full report
- dust
- Trust report
- Front-End-Checklist
- Trust report
Choose dust if…
- dust is primarily TypeScript; Front-End-Checklist is MDX.
- Tags unique to dust: agents, llm, large-language-models, rust.
- Also covers LLM Frameworks.
- dust ships Docker support for self-hosted deployment.
When NOT to use dust
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism.
- LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves.
- Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
Choose Front-End-Checklist if…
- Front-End-Checklist is primarily MDX; dust is TypeScript.
- 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: checklist, front-end-development, web-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 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.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (dust-tt/dust) · observed Jul 11, 2026
- GitHub forks (dust-tt/dust) · observed Jul 11, 2026
- Last push (dust-tt/dust) · observed Jul 11, 2026
- License file (MIT) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (thedaviddias/Front-End-Checklist) · observed Jul 11, 2026
- GitHub forks (thedaviddias/Front-End-Checklist) · observed Jul 11, 2026
- Last push (thedaviddias/Front-End-Checklist) · observed Jun 18, 2026
- License file (unknown) · observed Jul 11, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: dust 1.4k · Front-End-Checklist 73k (synced Jul 11, 2026).
Common questions
- What is the difference between dust and Front-End-Checklist?
- dust: Custom AI agent platform to speed up your work.. Front-End-Checklist: The essential checklist for modern web development, for humans and AI agents. See the comparison table for live GitHub stats and shared categories.
- When should I choose dust over Front-End-Checklist?
- Choose dust over Front-End-Checklist when dust is primarily TypeScript; Front-End-Checklist is MDX; Tags unique to dust: agents, llm, large-language-models, rust; Also covers LLM Frameworks; dust ships Docker support for self-hosted deployment.
- When should I choose Front-End-Checklist over dust?
- Choose Front-End-Checklist over dust when Front-End-Checklist is primarily MDX; dust is TypeScript; 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: checklist, front-end-development, web-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 avoid dust?
- AI Agents: Don't use an agent loop when a deterministic workflow would do; agents add latency, cost, and non-determinism. LLM Frameworks: Avoid a framework for a single prompt-and-retrieve call; the abstraction can cost more than it saves. Developer Tools: A gateway is overkill when you're pinned to a single provider and model.
- 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.
- Is dust or Front-End-Checklist more popular on GitHub?
- Front-End-Checklist has more GitHub stars (73,183 vs 1,413). Stars measure visibility, not whether either tool fits your constraints.
- Are dust and Front-End-Checklist open source?
- Yes - both are open-source projects on GitHub.
- Where can I find alternatives to dust or Front-End-Checklist?
- GraphCanon lists graph-backed alternatives at dust alternatives and Front-End-Checklist alternatives (dust markdown twin, Front-End-Checklist markdown twin), 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 mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, dust or Front-End-Checklist?
- dust: Very active. Front-End-Checklist: 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 dust and Front-End-Checklist?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: dust trust report; Front-End-Checklist trust report.