Repo brief: glideapps/glide-data-grid

Generated by RepoPilot · document generated 2026-09-17 · concise human review Evidence snapshot · analyzed 2026-09-17T03:09:57.710Z · commit 0875d78cc415

Verdict

Mixed — Slowing — last commit 7mo ago

• Last commit 7mo ago
• 15 active contributors
• Distributed ownership (top contributor 46% of recent commits)
• MIT licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

Glide Data Grid is a React component library that renders millions of rows efficiently using canvas-based lazy rendering and native scrolling. It provides out-of-the-box support for 15+ cell types (text, numbers, images, markdown, dropdowns, date pickers, multi-select, tags, sparklines, etc.) with full editing capabilities, column resizing, row grouping, and merged cells—built as the foundation for Glide's own Data Editor product. Monorepo with 3 workspaces: packages/core (the main grid engine and data-editor component), packages/cells (15+ reusable cell renderers and editors), and packages/source (data source abstraction). Core contains lazy rendering logic, keybindings, copy-paste, row…

Start here

Open these first:

• packages/core/src/data-editor/data-editor.tsx — Main DataEditor component orchestrating grid state, events, and cell rendering—entry point for all grid interactions.
• packages/core/src/internal/data-grid/data-grid.tsx — Canvas-based rendering engine managing viewport, cell drawing, and performance optimizations for millions of rows.
• packages/core/src/internal/data-grid/render/data-grid-render.ts — Core rendering pipeline coordinating header, cell, line, and overlay drawing on canvas context.
• packages/core/src/data-editor/data-editor-keybindings.ts — Keyboard event handling and navigation logic defining interaction patterns across the grid.
• packages/cells/src/draw-fns.ts — Shared cell drawing utilities providing common rendering primitives for all cell types.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository, then run: npm install (installs all workspace dependencies), followed by npm run storybook to start the dev server with live component editing at port 9009. For testing React 18/19 compatibilit…

Daily commands:

npm run storybook starts Storybook with live watch on packages/core. npm run build compiles all workspaces. npm run test runs Jest tests in packages/core. npm run prod-storybook builds and serves static Storyboo…

…shortened for this brief.

Key cautions & unknowns

• Slowing — last commit 7mo ago
• Scorecard: marked unmaintained (0/10)
• 1. The project is a monorepo with interdependent workspaces (core, cells, source); npm install must succeed at root, and you may need to rebuild workspaces if dependencies change. 2. Storybook setup requires both…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.