yeraze/meshmonitorNew scan
98/ 100 · A

Polished and well engineered. Punching above its star count.

Web tool for monitoring Mesh Node Deployment over TCP/HTTP

TypeScript536 starsBSD-3-Clauseupdated today

Outstanding work. A score of 98/100 puts this repo in a very small tier of truly well-engineered open source projects.

DocumentationREADME, setup, examples, license
98
EngineeringTests, CI, linting, lockfiles
100
Project healthDescription, activity, stars, deps
92

What to fix first

The highest-impact improvements for this repo.

  1. 1
    Dependency manifest
    Project healthIssue

    Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.

  2. 2
    Dependency manifest
    Project healthIssue

    Add a `keywords` array to help people find your package on npm.

  3. 3
    Dependency manifest
    Project healthIssue

    Add a `homepage` field pointing to your docs or project website.

Detailed breakdown

Documentation

98
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions100
    • README documents how to install the project.
    • README documents how to run the project.
    • .env.example is present. Contributors can see exactly which env vars to set.
  • License100
    • Licensed under BSD-3-Clause.
  • Contributing guide88
    • Contributing guide is detailed and thorough.
    • Contributing guide lacks a setup section (−12 pts).Show new contributors how to get a local dev environment running.
    • Contributing guide describes code style expectations.
    • Contributing guide explains how to run tests.
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Optional: add a Code of Conduct.A CODE_OF_CONDUCT.md signals that your project is welcoming. GitHub has a template you can add in one click.

Engineering

100
  • Tests100
    • Test files detected (src/App.test.tsx).
  • CI/CD100

    Not applicable?

    • CI is configured (.github/workflows/ci.yml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI workflow runs a lint or format check.
    • CI runs type checking (tsc, mypy, cargo check, etc.).
    • CI reports or uploads test coverage.
    • CI caches dependencies for faster runs.
    • CI tests across multiple environments or versions.
    • CI includes a build step.
  • Linting and formatting100
    • Linter or formatter configured (.prettierrc).
  • Reproducibility100
    • Lockfile present (package-lock.json). Installs are reproducible.
    • Environment pinned via .devcontainer/Dockerfile.
    • Dockerfile uses multi-stage builds (smaller, more secure images).
    • Dependabot covers 3 ecosystems (npm, github-actions, docker). Dependencies stay current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

92
  • Dependency manifest75
    • Dependency manifest found (package.json).
    • package.json has a description field.
    • package.json has no repository field (−10 pts).Add a `repository` field pointing to the GitHub URL so npm knows where the source lives.
    • package.json has no keywords (−8 pts).Add a `keywords` array to help people find your package on npm.
    • package.json has no homepage field (−7 pts).Add a `homepage` field pointing to your docs or project website.
  • Repository metadata100
    • Repository has a description.
    • Primary language detected: TypeScript.
  • Activity100
    • Actively maintained (pushed within the last month).
    • 536 stars.
  • Housekeeping100
    • .gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 67
    Forks
  • 344
    Releaseslatest 8mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 536
    Watchers

Responsiveness

  • 3h
    Median issue response
  • <1h
    Median PR merge time
  • 9
    Open issues
Repository files69 root entries
  • .claude
  • .devcontainer
    Good: Environment pinned via .devcontainer/Dockerfile.
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Dependabot covers 3 ecosystems (npm, github-actions, docker). Dependencies stay current.
    Good: Issue or PR templates present.
  • .superpowers
  • desktop
  • docker
  • docs
  • examples
  • helm
  • lxc
  • public
  • scripts
  • src
    Good: Test files detected (src/App.test.tsx).
  • tests
  • tiles
  • tools
  • .dockerignore
  • .env.example
  • .env.production.example
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .npmrc
  • .prettierrc
    Good: Linter or formatter configured (.prettierrc).
  • ARCHITECTURE.md
  • CHANGELOG.md
  • check-admin.mjs
  • CLAUDE.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.
    Good: Contributing guide describes code style expectations.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • copy-telemetry.mjs
  • docker-compose.ble.yml
  • docker-compose.dev.yml
  • docker-compose.local.yml
  • docker-compose.production.yml
  • docker-compose.rpi.yml
  • docker-compose.test.yml
  • docker-compose.upgrade-test.yml
  • docker-compose.upgrade.yml
  • docker-compose.yml
  • docker-simple.yml
  • Dockerfile
  • Dockerfile.armv7
  • Dockerfile.proxy
  • embed.html
  • eslint.config.mjs
  • export.yaml
  • generate-vapid-keys.js
  • index.html
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • logfile.txt
  • message.txt
  • nginx.conf
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • PLAN.md
  • protobufs
  • proxy-start.sh
  • 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.
  • RELEASE_NOTES.md
  • reset-admin.mjs
  • SECURITY.md
    Good: Security policy present.
  • start.sh
  • test-telemetry-fix.mjs
  • TODOS.md
  • tsconfig.json
  • tsconfig.node.json
  • tsconfig.server.json
  • vite.config.ts
  • vitest.config.ts