A concise API for exploratory data visualization implementing a layered grammar of graphics
Reliability breakdown
Component scores measured daily from GitHub activity (2026-04-17).
Activity on 0 of 17 tracked days in the last 90 and 0 of 8 in the last 30.
Merged 0 of 0 PRs opened and closed 0 of 0 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
0 releases in the last 180 days, 0 in the last 90 and 0 in the last 30 — a steady cadence scores highest.
Last push 7 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Apr 12, 2026
Current13
Previous6
Weekly star gains
GitHub GraphQL current stargazer cohort, reconstructed from starredAt events and totalCount retrieved in one stable pagination walk. GitHub does not expose historical unstar events, so this is not an exact ledger of past star counts.
103 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current0
Previous4
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
86 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current12
Previous11
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
86 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current10
Previous6
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
86 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current18
Previous23
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
86 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 12, 2026
Current13
Previous14
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
86 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Apr 13, 2026
Current0.00
Previous0.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
6 observed daily rows. Missing days are not fabricated.
Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).
| Date | Issues opened | Issues closed | Stored score |
|---|
Apr 16, 2026
Current2.00
Previous0.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
33 observed daily rows. Missing days are not fabricated.
Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).
| Date | PRs opened | PRs closed | Stored score |
|---|
Join the conversation
Share what you know about plot — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting plot.
Project Q&A
Browse implementation threads tied directly to observablehq/plot. Each question links through to the full answer page.
Be the first to ask how teams run plot in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses plot — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post