Good shape overall. A few tweaks would push it into the top tier.

An open source MSP PSA from Nine Minds

Documentation

95

README12pt90

README is present.

Contributing guide5pt92

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

61

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 (ee/appliance/host-service/tests).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/circular-deps.yml).

Linting and formatting5pt100

Linter or formatter configured (ee/extensions/softwareone-ext/.eslintrc.json).

Project health

92

Dependency manifest6pt75

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)
  • 42
    Forks
  • 35
    Releaseslatest 1y ago

Community

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

Responsiveness

  • 22h
    Median issue response
  • <1h
    Median PR merge time
  • 34
    Open issues
Repository files88 root entries
  • .crew
  • .github
    Good: CI is configured (.github/workflows/circular-deps.yml).
    Good: Environment pinned via .github/docker-compose.yaml.
  • .impeccable
  • cli
  • docker
  • docs
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • ee
    Good: Test files detected (ee/appliance/host-service/tests).
    Good: Linter or formatter configured (ee/extensions/softwareone-ext/.eslintrc.json).
  • eslint-plugin-custom-rules
  • extensions
  • helm
  • hocuspocus
  • packages
  • pgbouncer
  • redis
  • scripts
  • sdk
  • server
  • services
  • setup
  • shared
  • test-config
  • tools
  • types
  • .dockerignore
  • .env.e2e
  • .env.example
  • .env.localtest
  • .env.runner
  • .env.runner.example
  • .gitignore
    Good: .gitignore present.
  • .npmrc
  • .nvmrc
  • .nxignore
  • app.json
  • ARCHITECTURE_FIX.md
  • assemblyscript-0.27.36.tgz
  • compose.env
  • context.md
  • DESIGN.md
  • devbox.json
  • devbox.lock
  • docker-compose.base.yaml
  • docker-compose.ce.yaml
  • docker-compose.e2e-local.yaml
  • docker-compose.e2e-simple.yaml
  • docker-compose.e2e-with-worker.yaml
  • docker-compose.e2e.yaml
  • docker-compose.ee.yaml
  • docker-compose.imap-test.yaml
  • docker-compose.imap.ce.yaml
  • docker-compose.minio-dev.yaml
  • docker-compose.ngrok.yaml
  • docker-compose.override.yaml
  • docker-compose.playwright-deps.yaml
  • docker-compose.playwright-workflow-deps.yml
  • docker-compose.playwright.yml
  • docker-compose.prebuilt.base.yaml
  • docker-compose.prebuilt.ce.yaml
  • docker-compose.prebuilt.ee.yaml
  • docker-compose.prod.yaml
  • docker-compose.runner-dev.yml
  • docker-compose.setup-ubuntu.override.yaml
  • docker-compose.test-citus.yaml
  • docker-compose.test-minio.yaml
  • docker-compose.test.yml
  • docker-compose.yaml
  • Dockerfile
  • Dockerfile.build
  • Dockerfile.dev
  • Dockerfile.test
  • eas.json
  • environment.txt
  • eslint.config.js
  • LICENSE.md
    Good: Licensed under Other.
  • Makefile
  • nx.json
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
  • research.md
  • rust-toolchain.toml
  • server-dev-entrypoint.sh
  • skip-budget.json
  • translation-report.txt
  • tsconfig.base.json
  • tsconfig.json
  • vitest.config.ts