bulwarkmail/webmail
Grade a repo

72

/ 100

GradeC

Solid engineering. The biggest lever is test coverage.

Top 43% of 5,156 graded repos

JMAP Webmail built for the 21st Century. A modern, self-hosted email client for Stalwart Mail Server powered by the JMAP protocol. Email, calendar, contacts and files. Fast, private, and open source.

Documentation99
Engineering44
Health100
TypeScript773Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  4. 4
    CI/CD14pt

    Add a lint step to catch style issues automatically.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

99

Contributing guide5pt92

Contributing guide is detailed and thorough.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

44

Issue and PR templates6pt0

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.

Tests18pt35

Test files detected (components/contacts/__tests__).

CI/CD14pt40

CI is configured (.github/workflows/docker-publish-releases.yml).

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

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

Project health

100

Dependency manifest6pt100

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

  • 135 / 696
    Commits (30d / 90d)
  • 111
    Forks
  • 36
    Releaseslatest 4mo ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 773
    Watchers

Responsiveness

  • 6h
    Median issue response
  • 2h
    Median PR merge time
  • 81
    Open issues
Repository files40 root entries
  • .github
    Good: CI is configured (.github/workflows/docker-publish-releases.yml).
  • .husky
  • app
  • components
    Good: Test files detected (components/contacts/__tests__).
  • contexts
  • e2e
  • hooks
  • i18n
  • lib
  • locales
  • public
  • screenshots
  • stores
  • .dockerignore
  • .env.dev.example
  • .env.example
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Good: Contributing guide describes code style expectations.
    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.
    Good: Contributing guide includes code examples.
  • docker-compose.yml
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • eslint.config.mjs
    Good: Linter or formatter configured (eslint.config.mjs).
  • FEATURES.md
  • instrumentation.node.ts
  • instrumentation.ts
  • LICENSE
    Good: Licensed under Other.
  • next.config.ts
  • NOTICE
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • postcss.config.mjs
  • proxy.ts
  • 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.
  • setup.sh
  • tailwind.config.ts
  • tsconfig.json
  • VERSION
  • vitest.config.ts
  • vitest.setup.ts
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/bulwarkmail/webmail)](https://www.repo-grade.com/report/bulwarkmail/webmail)

More graded TypeScript repos