Comparison
automa vs simple-chromium-ai
Verdict
Pick automa if automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms; pick simple-chromium-ai if the simple-chromium-ai library offers TypeScript developers a way to run Local Large Language Models directly within Chromium browsers.
Markdown twin · automa alternatives · simple-chromium-ai alternatives
GraphCanon updated Sep 20, 2026
11views this month
vs
Trust & integrity
| Signal | automa | simple-chromium-ai |
|---|---|---|
| Maintenance | Slowing (195d since push) As of Sep 14, 2026 · github_public_v1 | Steady (39d since push) As of Sep 20, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 14, 2026 · github_public_v1 | Not a fork · Personal account As of Sep 20, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 15, 2026 · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- automa
- A browser extension for automating your browser by connecting blocks
- simple-chromium-ai
- TypeScript library for executing local LLM in Chromium browsers
Stars
- automa
- 22k
- simple-chromium-ai
- 268
Forks
- automa
- 2.3k
- simple-chromium-ai
- 14
Open issues
- automa
- 377
- simple-chromium-ai
- 11
Language
- automa
- Vue
- simple-chromium-ai
- TypeScript
Adopt for
- automa
- Automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms.
- simple-chromium-ai
- The simple-chromium-ai library offers TypeScript developers a way to run Local Large Language Models directly within Chromium browsers.
Persona
- automa
- -
- simple-chromium-ai
- -
Runtime
- automa
- -
- simple-chromium-ai
- -
License
- automa
- Other
- simple-chromium-ai
- MIT
Last pushed
- automa
- Mar 2, 2026
- simple-chromium-ai
- Aug 11, 2026
Categories
- automa
- Developer Tools
- simple-chromium-ai
- Developer Tools, LLM Frameworks
Trust and health
Maintenance
- automa
- Slowing (36%)
- simple-chromium-ai
- Steady (60%)
Days since push
- automa
- 195d
- simple-chromium-ai
- 39d
Open issues (now)
- automa
- 377
- simple-chromium-ai
- 11
Stars delta
- automa
- +73 (30d)
- simple-chromium-ai
- +1 (30d)
Open issues delta
- automa
- +5 (30d)
- simple-chromium-ai
- 0 (30d)
Owner type
- automa
- Organization
- simple-chromium-ai
- User
Full report
- automa
- Trust report
- simple-chromium-ai
- Trust report
Choose automa if…
- automa is primarily Vue; simple-chromium-ai is TypeScript.
- License: automa is Other, simple-chromium-ai is MIT.
- Tags unique to automa: automation, browser-automation, firefox-extension, hacktoberfest.
- If you are working with Chrome or Firefox browsers and require the capability to interconnect blocks to automate repetitive, browser-based actions.
When NOT to use automa
- When specific automation tasks demand customization via coding rather than block connectivity since Automa is more suited for visual scripting.
- If your project involves non-browser-based workflows, as Automa's functionality is limited to browser extensions like Chrome and Firefox.
Choose simple-chromium-ai if…
- simple-chromium-ai is primarily TypeScript; automa is Vue.
- License: simple-chromium-ai is MIT, automa is Other.
- Tags unique to simple-chromium-ai: browser-extension, chrome, chromium, gemini-nano-in-chrome.
- Also covers LLM Frameworks.
- When you need to integrate local LLM capabilities into web applications that are run in Chromium-based browsers, such as Chrome and Edge.
When NOT to use simple-chromium-ai
- In cases where the application must support a variety of non-Chromium browsers without significant fallback mechanisms for alternative browser engine integration.
- If the development team prioritizes JavaScript over TypeScript and considers the type checking overhead unnecessary or cumbersome.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (AutomaApp/automa) · observed Sep 20, 2026
- GitHub forks (AutomaApp/automa) · observed Sep 20, 2026
- Last push (AutomaApp/automa) · observed Mar 2, 2026
- License file (Other) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- GitHub stars (kstonekuan/simple-chromium-ai) · observed Sep 20, 2026
- GitHub forks (kstonekuan/simple-chromium-ai) · observed Sep 20, 2026
- Last push (kstonekuan/simple-chromium-ai) · observed Aug 11, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: automa 22k · simple-chromium-ai 268 (synced Sep 20, 2026).
Common questions
- What is the difference between automa and simple-chromium-ai?
- automa: A browser extension for automating your browser by connecting blocks. simple-chromium-ai: TypeScript library for executing local LLM in Chromium browsers. See the comparison table for live GitHub stats and shared categories.
- When should I choose automa over simple-chromium-ai?
- Choose automa over simple-chromium-ai when automa is primarily Vue; simple-chromium-ai is TypeScript; License: automa is Other, simple-chromium-ai is MIT; Tags unique to automa: automation, browser-automation, firefox-extension, hacktoberfest; If you are working with Chrome or Firefox browsers and require the capability to interconnect blocks to automate repetitive, browser-based actions.
- When should I choose simple-chromium-ai over automa?
- Choose simple-chromium-ai over automa when simple-chromium-ai is primarily TypeScript; automa is Vue; License: simple-chromium-ai is MIT, automa is Other; Tags unique to simple-chromium-ai: browser-extension, chrome, chromium, gemini-nano-in-chrome; Also covers LLM Frameworks; When you need to integrate local LLM capabilities into web applications that are run in Chromium-based browsers, such as Chrome and Edge.
- When should I avoid automa?
- When specific automation tasks demand customization via coding rather than block connectivity since Automa is more suited for visual scripting. If your project involves non-browser-based workflows, as Automa's functionality is limited to browser extensions like Chrome and Firefox.
- When should I avoid simple-chromium-ai?
- In cases where the application must support a variety of non-Chromium browsers without significant fallback mechanisms for alternative browser engine integration. If the development team prioritizes JavaScript over TypeScript and considers the type checking overhead unnecessary or cumbersome.
- Is automa or simple-chromium-ai more popular on GitHub?
- automa has more GitHub stars (21,619 vs 268). Stars measure visibility, not whether either tool fits your constraints.
- Are automa and simple-chromium-ai open source?
- Yes - both are open-source projects on GitHub (automa: Other, simple-chromium-ai: MIT).
- Where can I find alternatives to automa or simple-chromium-ai?
- GraphCanon lists graph-backed alternatives at automa alternatives and simple-chromium-ai alternatives (automa markdown twin, simple-chromium-ai 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, automa or simple-chromium-ai?
- automa: Slowing. simple-chromium-ai: Steady. 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 automa and simple-chromium-ai?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: automa trust report; simple-chromium-ai trust report.