Item detail
github.com

slothflowlabs/duckle

RepoRadar surfaced slothflowlabs/duckle — a developer tool — into the Data Tooling section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.3 out of 10.

Score8.2
Popularity100.0
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum7.0
Maturity8.9
Open-source/build8.4
Evidence8.0
Workflow potential9.3
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for builders who want an AI-assisted data pipeline workbench without giving up local execution, plain files, or direct control over the generated SQL and connector flow.

Who should use it

Data engineers who want a local-first pipeline studio instead of a hosted ETL control plane Analytics teams prototyping DuckDB-based workflows before deciding whether they need a heavier orchestrator Developers who want AI help with connector and transform setup without surrendering local execution Teams that prefer git-friendly workspace files over opaque browser-only pipeline builders

Who should skip it

Pass on slothflowlabs/duckle if its scope or audience does not match what your team is building right now.

About this signal

slothflowlabs/duckle is tracked by RepoRadar as a developer tool in the Data Tooling section. First seen 2026-06-27; the source record was last checked on 2026-06-27. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, slothflowlabs/duckle is strongest on workflow potential (9.3) and maturity (8.9) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The slothflowlabs/duckle record combines a 8.2/10 composite score with separate popularity (100.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Questions worth asking before you adopt this

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

The assistant and connector layer can still see query text, schema details, and local workspace context, so start with non-sensitive datasets until you understand what the app stores and sends; A 290-plus connector surface and built-in scheduler can expand the blast radius quickly if credentials are over-scoped, so review each connector and destination before production use; The repo does not ship a root LICENSE file and instead declares the dual MIT OR Apache-2.0 terms in Cargo workspace metadata, so downstream teams should pin the exact release artifacts they reviewed.

Evidence links
Closest alternatives / related signals
duckdb etl elt local-first data-tooling desktop-app mit-or-apache ai-assistant
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-10-10T17:09:29.745535Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

83 dated snapshots retained from 2026-06-27 through 2026-10-10; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.2 current · +0.0 net
Repository momentum9.0 current · +2.0 net
GitHub stars (observed)1,499 current · +716 net
GitHub stars1,499 exact observation
Versionv0.7.4
Last release2026-09-25T09:01:04Z
MaintenanceActive
Current riskConditional
Current verdictTry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineModel Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-10-108.29.01,499ConditionalTry nowActive
2026-10-098.29.01,497ConditionalTry nowActive
2026-10-088.29.31,493ConditionalTry nowActive
2026-10-078.29.01,489ConditionalTry nowActive
2026-10-068.29.01,487ConditionalTry nowActive
2026-10-058.29.61,478ConditionalTry nowActive
2026-10-038.29.01,350ConditionalTry nowActive
2026-10-028.29.01,345ConditionalTry nowActive
2026-10-018.29.01,343ConditionalTry nowActive
2026-09-308.29.01,338ConditionalTry nowActive
2026-09-298.29.01,338ConditionalTry nowActive
2026-09-288.29.31,333ConditionalTry nowActive

Why the record changed

Stars change

Stars changed: 1498 → 1499.

Stars change

Stars changed: 1497 → 1498.

Stars change

Stars changed: 1496 → 1497.

Stars change

Stars changed: 1493 → 1496.

Stars change

Stars changed: 1489 → 1493.

Stars change

Stars changed: 1488 → 1489.

Stars change

Stars changed: 1487 → 1488.

Stars change

Stars changed: 1485 → 1487.

Stars change

Stars changed: 1478 → 1485.

Stars change

Stars changed: 1350 → 1478.

Stars change

Stars changed: 1348 → 1350.

Stars change

Stars changed: 1345 → 1348.