npm/statusboard

Public monitor/status/health board for @npm/cli-team's maintained projects

Owned by npm · part of Microsoft

View on GitHub ↗Jump to charts ↓

npm/statusboard has 200+ stars and 70+ forks on GitHub, is written in JavaScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 29 minutes ago
Added to GitGenius on October 12th, 2026
Created on September 5th, 2019
Open Issues & Pull Requests: 72 (+0)
GitHub issues: Enabled
Number of forks: 75
Total Stargazers: 211 (+0)
Total Subscribers: 18 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 30.1 days
Mean response time: 233.5 days
90th percentile: 1080.0 days
Tracked items: 78

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 619 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • chore (4)
  • epic (4)
  • feature (4)
  • invalid (4)
  • audit-policies-filters (2)
  • initiative (2)
  • Enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

npm statusboard is a public monitoring dashboard that aggregates the status and health of a team's open-source projects in a single view.

The tool solves the problem of tracking project health across multiple repositories by automatically discovering and monitoring projects that belong to an organization and are tagged with a specific topic. It fetches data daily from GitHub and the npm registry, collecting metrics about each project's status. The dashboard displays this aggregated information through a web interface, allowing team members to quickly assess the overall health of their maintained projects without visiting each repository individually.

The statusboard is designed for teams maintaining multiple open-source projects who want centralized visibility into their portfolio. It works best for organizations using GitHub where projects can be tagged with a consistent topic for discovery. The tool is portable enough that other teams can fork and adapt it for their own use, though doing so requires updating configuration files, GitHub Actions workflows, and data storage paths to match a different organization's structure and naming conventions.

The project uses a monorepo structure with separate workspaces for data fetching and web serving. Development involves running fetch commands locally to update project lists and daily metrics, with corresponding GitHub Actions workflows available for automation. The site publishes automatically to GitHub Pages on pushes to the main branch. The tool maintains historical data in JSON files and provides configuration points for controlling which data gets fetched from GitHub and how it gets parsed and displayed on the frontend.