All 75 Dependencies
Every package BaseBuddy depends on, ranked by repo health score.
Most CMS platforms require your content to fit their schema; BaseBuddy inverts that relationship by mapping onto whatever Postgres or Supabase tables you already have. You run one BaseBuddy instance, complete onboarding (via the UI or CLI), map existing tables to editable fields, and start editing — the saved mapping becomes the runtime source of truth, and your content database stays exactly as it was, under your own control.
This matters for teams with content already living in application tables (posts, pages, docs, guides) that don't want to migrate into a CMS-specific schema just to get a decent editing UI. BaseBuddy provides a TipTap-based, WordPress-like editing experience on top of those existing tables instead.
AGPL-3.0 licensed and self-hosted, BaseBuddy is a young, small project (single-digit stars at time of review) but addresses a specific, well-defined gap between "raw database editing" and "migrate everything into a dedicated CMS."