Item detail
github.com

qataruts/monlite

RepoRadar surfaced qataruts/monlite — an agent project — into the Developer Infra section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.7 out of 10.

Score8.2
Popularity1.0
Risknone
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum6.0
Maturity6.5
Open-source/build8.4
Evidence8.0
Workflow potential9.7
Setup ease8.8

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

Why it matters

Useful for builders who are tired of spinning up MongoDB, Redis, Qdrant, and BullMQ just to prototype an agent or RAG service on one machine.

Who should use it

Developers prototyping local RAG and agent backends without Docker-heavy service stacks TypeScript teams that want SQLite-native documents, vectors, queues, and cron in one package family Builders shipping offline-capable or edge-adjacent AI tooling with a simpler persistence layer Teams exploring a single-file backend for agent memory, task orchestration, and retrieval

Who should skip it

Skip qataruts/monlite if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

qataruts/monlite is tracked by RepoRadar as an agent project in the Developer Infra section. First seen 2026-06-29; the source record was last checked on 2026-06-29. The current verdict is 'try now' with a Gold tier and easy setup difficulty. qataruts/monlite leads on workflow potential (9.7) and setup ease (8.8); its lowest signal is momentum (6.0), so factor that in before investing setup time. 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 qataruts/monlite record combines a 8.2/10 composite score with separate popularity (1.0), risk (none), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.

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

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
agents sqlite rag vector-search queue mit
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

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 →

36 dated snapshots retained from 2026-06-29 through 2026-08-13; 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 momentum5.5 current · -0.5 net
GitHub stars (observed)37 current · +0 net
GitHub stars37 exact observation
Version[email protected]
Last release2026-06-29T19:36:34Z
Maintenancemaintained
Current risknone
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.25.537nonetry nowmaintained
2026-08-128.27.537nonetry nowactive
2026-08-118.27.537nonetry nowactive
2026-08-108.27.537nonetry nowactive
2026-08-098.27.537nonetry nowactive
2026-08-088.27.537nonetry nowactive
2026-08-078.27.537nonetry nowactive
2026-08-068.26.0Not recordednonetry nownot recorded
2026-08-058.26.0Not recordednonetry nownot recorded
2026-08-048.27.537nonetry nowactive
2026-08-038.27.537nonetry nowactive
2026-08-028.27.537nonetry nowactive

Why the record changed

maintenance changed

Maintenance changed: active → maintained.