Polished and well engineered. Punching above its star count.

A simple app to manage your calendar & tasks.

Documentation

89

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

95

CI/CD14pt85

CI is configured (.github/workflows/test-e2e.yml).

Reproducibility6pt92

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

Tests18pt100

Test files detected (e2e/allday/create-allday-event-keyboard.spec.ts).

Linting and formatting5pt100

Linter or formatter configured (biome.json).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

89

Dependency manifest6pt65

Dependency manifest found (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)
  • 67
    Forks
  • 8
    Releaseslatest 10d ago

Community

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

Responsiveness

  • 14d 20h
    Median issue response
  • 1d 11h
    Median PR merge time
  • 107
    Open issues
Repository files36 root entries
  • .agents
  • .claude
  • .codex
  • .cursor
  • .cursorrules
  • .github
    Good: CI is configured (.github/workflows/test-e2e.yml).
    Good: Dependabot configured for npm.
    Good: Issue or PR templates present.
  • .impeccable
  • docs
  • e2e
    Good: Test files detected (e2e/allday/create-allday-event-keyboard.spec.ts).
  • packages
  • self-host
    Good: Environment pinned via self-host/compose.yaml.
  • .dockerignore
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • babel.config.js
  • biome.json
    Good: Linter or formatter configured (biome.json).
  • bun.lock
    Good: Lockfile present (bun.lock). Installs are reproducible.
  • bunfig.toml
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • compass.example.yaml
  • CONTEXT.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • DESIGN.md
  • jest-mongodb-config.js
  • jest.config.js
  • lerna.json
  • LICENSE
    Good: Licensed under MIT.
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • PRODUCT.md
  • 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.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • skills-lock.json
  • tsconfig.json