Popular for its size, but the engineering basics lag behind the interest.

Parula - New full-featured desktop email, chat and video conference client

Documentation

65

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

README12pt55

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

51

Reproducibility6pt0

No dependency lockfile found (−70 pts).

Commit package-lock.json, pnpm-lock.yaml, yarn.lock, or bun.lock so Node installs are repeatable.

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.

CI/CD14pt40

CI is configured (.github/workflows/auto-translate.yml).

Tests18pt80

Test files detected (app/logic/Calendar/RecurrenceRule.test.ts).

Linting and formatting5pt100

Linter or formatter configured (desktop/.editorconfig).

Project health

100

Dependency manifest6pt100

Dependency manifest found (app/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)
  • 14
    Forks
  • 111
    Releaseslatest 1y ago

Community

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

Responsiveness

  • 4d 10h
    Median issue response
  • 8h
    Median PR merge time
  • 256
    Open issues
Repository files11 root entries
  • .github
    Good: CI is configured (.github/workflows/auto-translate.yml).
  • .vscode
  • app
    Good: Test files detected (app/logic/Calendar/RecurrenceRule.test.ts).
    Good: Dependency manifest found (app/package.json).
  • desktop
    Good: Linter or formatter configured (desktop/.editorconfig).
  • docs
  • lib
  • mobile
  • runner
  • .gitignore
    Good: .gitignore present.
  • LICENSE
    Good: Licensed under Other.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.