Well engineered for its size. A portfolio piece worth showing off.
The best open-source alternative to Notion
Documentation
90
Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.
→ Add setup instructions, code style notes, and how to run tests.
README is present.
README documents how to install the project.
Licensed under Apache-2.0.
Engineering
85
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
Lockfile present (yarn.lock). Installs are reproducible.
Test files detected (docs/src/App.test.tsx).
CI is configured (.github/workflows/ci.yml).
Linter or formatter configured (eslint.config.mjs).
Project health
98
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 0Forks
- 84Releaseslatest 4mo ago
Community
- —Community health
- —authors own >50% of commits
- 27Watchers
Responsiveness
- —Median issue response
- 11hMedian PR merge time
- 1Open issues
Repository files41 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/ci.yml).
- .husky
- .storybook
- codemod
- docsGood: Test files detected (docs/src/App.test.tsx).
- packages
- public
- scripts
- src
- static
- test
- types
- .env.example
- .gitignoreGood: .gitignore present.
- .jscpdrc.json
- .nvmrcGood: Environment pinned via .nvmrc.
- .yarnrc.yml
- CHANGELOG.md
- chromatic.config.json
- CLAUDE.md
- CODEOWNERS
- commitlint.config.js
- CONTRIBUTING.mdIssue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.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.
- eslint.config.mjsGood: Linter or formatter configured (eslint.config.mjs).
- index.html
- LICENSEGood: Licensed under Apache-2.0.
- MIGRATION.md
- NOTICE
- package.jsonGood: Dependency manifest found (package.json).
- playwright.config.ts
- README.mdGood: 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.
- serve.json
- tsconfig.json
- vite-env.d.ts
- vite.config.iife.mjs
- vite.config.mjs
- vite.config.umd.mjs
- vitest.config.ts
- vitest.shims.d.ts
- yarn.lockGood: Lockfile present (yarn.lock). Installs are reproducible.