Polished and well engineered. Punching above its star count.

An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time.

Documentation

100

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Contributing guide5pt100

Contributing guide is detailed and thorough.

Engineering

85

Tests18pt80

Test files detected (assistant/__tests__).

Reproducibility6pt80

Lockfile present (assistant/bun.lock). Installs are reproducible.

CI/CD14pt83

CI is configured (.github/workflows/build-chrome-extension.yaml).

Linting and formatting5pt100

Linter or formatter configured (assistant/eslint.config.mjs).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (assistant/examples/plugins/echo/package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • Commits (30d / 90d)
  • 114
    Forks
  • 127
    Releaseslatest 4mo ago

Community

  • Community health
  • authors own >50% of commits
  • 744
    Watchers

Responsiveness

  • <1h
    Median issue response
  • <1h
    Median PR merge time
  • 125
    Open issues
Repository files38 root entries
  • .claude
  • .cursor
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/build-chrome-extension.yaml).
    Good: Issue or PR templates present.
  • .vscode
  • assets
  • assistant
    Good: Test files detected (assistant/__tests__).
    Good: Linter or formatter configured (assistant/eslint.config.mjs).
    Good: Lockfile present (assistant/bun.lock). Installs are reproducible.
    Good: Environment pinned via assistant/Dockerfile.
    Good: Dependency manifest found (assistant/examples/plugins/echo/package.json).
  • benchmarking
  • cli
  • clients
  • credential-executor
  • docs
  • evals
  • gateway
  • meta
  • packages
  • plugins
  • scripts
  • skills
  • .dockerignore
  • .env.example
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .nvmrc
  • .tool-versions
  • AGENTS.md
  • ARCHITECTURE.md
  • bunfig.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONSTITUTION.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • GLOSSARY.md
  • LICENSE
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • setup.sh
  • socket.yml
  • test-preload.ts