Skip to content

*Database Automation, Testing, and Alignment* for Supabase projects. D.A.T.A. is what you get when you need an android-level precision tool for database operations. Like Lt. Commander Data himself, this CLI won't let you violate the Prime Directive of production safety.

active 2025-08-302025-09-02 (UTC)

Partial coverage20,533 / 26,289 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-14 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
56
Pushes
15
Pull requests
2
Issues
27
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 4 days from 2025-08-30 to 2025-09-02. Pushes: 15 total, peak 8 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 27 total, peak 10 in a day. Comments: 8 total, peak 5 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
flyingrobots481515
taralamia2011
claude[bot]1001
RiteshJha9121001

Recent activity

Latest issues, pull requests and releases

  • Issue#9flyingrobots2025-09-02 17:15
    Add test coverage for migrate-generate command
  • Issue#10flyingrobots2025-09-02 17:15
    Add test coverage for migrate-promote command
  • Issue#6flyingrobots2025-09-02 17:15
    Standardize error types across test coverage modules
  • Issue#7flyingrobots2025-09-02 17:15
    Replace console methods with proper logging levels
  • Issue#8flyingrobots2025-09-02 17:15
    Add test coverage for CompileCommand
  • Issue#3flyingrobots2025-09-02 17:15
    Add comprehensive end-to-end integration tests for coverage enforcement
  • Issue#4flyingrobots2025-09-02 17:15
    Fix inconsistent async/await and promise patterns
  • Issue#5flyingrobots2025-09-02 17:15
    Optimize performance for large schema analysis and test scanning
  • Issue#2flyingrobots2025-09-02 17:15
    Add coverage enforcement configuration to datarc.schema.json
  • Issue comment#20taralamia2025-09-02 09:08
    Refactor/testing typed errors issue6
  • Issue comment#20flyingrobots2025-09-02 02:52
    Refactor/testing typed errors issue6
  • Issue comment#14flyingrobots2025-09-01 18:32
    Add test coverage for MigrationOrchestrator
  • Issue#14flyingrobots2025-09-01 18:32
    Add test coverage for MigrationOrchestrator
  • Issue comment#13flyingrobots2025-09-01 18:31
    Add test coverage for SupabaseCommand base class
  • Issue comment#12flyingrobots2025-09-01 18:31
    Add test coverage for DatabaseCommand base class
  • Issue comment#23flyingrobots2025-09-01 17:45
    Refactor core
  • Pull request#23flyingrobots2025-09-01 17:36
  • Issue comment#20claude[bot]2025-09-01 11:34
    Refactor/testing typed errors issue6
  • Pull request#20taralamia2025-09-01 11:13
  • Issue comment#7RiteshJha9122025-08-31 16:05
    Replace console methods with proper logging levels
  • Issue#1flyingrobots2025-08-31 15:19
    [CRITICAL] Complete Runtime Migration from Node.js to Deno for Edge Function Parity
  • Issue#18flyingrobots2025-08-31 01:05
    Audit and refactor codebase to enforce one-class-per-file policy
  • Issue#16flyingrobots2025-08-31 00:28
    Add test coverage for CoverageEnforcer
  • Issue#14flyingrobots2025-08-31 00:27
    Add test coverage for MigrationOrchestrator
  • Issue#13flyingrobots2025-08-31 00:27
    Add test coverage for SupabaseCommand base class

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.