Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for data engineering teams, analytics engineers, AI-curious readers tracking enterprise data agent releases, engineering teams running multi-table analyses against enterprise datasources, and any developer wiring an AI coding agent to an enterprise-grade data workbench -- and who can pair datagallery-lab/datafoundry with TypeScript 5.x + Node.js + pnpm for the build surface, the 28 supporte
Who should use it
Who should skip it
Skip datagallery-lab/datafoundry if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
datagallery-lab/datafoundry is tracked by RepoRadar as a apache-2.0 enterprise-grade data in the DataFoundry: Enterprise Data Agent Workbench (28 section. It was first seen on 2026-07-07 and last updated on 2026-07-07. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, datagallery-lab/datafoundry is strongest on workflow potential (9.5) and practical usefulness (9.0) and weakest on maturity (6.3) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned datagallery-lab/datafoundry a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 121* / 20-fork repo is at active maintenance but the status badge is `early but usable` per the README -- the project is real and runnable but new; the consumer SHOULD benchmark the agent on the consumer's specific enterprise data questions before relying on the workbench in production; the consumer SHOULD review the credential isolation and field masking before deploying on production data; the consumer SHOULD review the event stream retention policy (the stream can grow over time).