Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most startup founders + small-team engineering managers + knowledge-base power users building their 'second brain' on top of an AI agent today have been either (a) using a closed-source proprietary note-taking + AI tool (Notion AI + Obsidian Sync + Reflect + Mem) that locks the consumer into the vendor's pricing + AI features + data export format + sync semantics, (b) hand-rolling a custom Obsidia
Who should use it
Who should skip it
Consider cabinetai/cabinet lower priority if you already have a working solution in this category.
About this signal
cabinetai/cabinet is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-09 and last updated on 2026-07-09. The current verdict is 'try now' with a Silver tier and easy setup difficulty. The standout signals for cabinetai/cabinet are momentum (9.0) and setup ease (8.8), while maturity (5.7) trails — that balance shapes where it fits best. 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 cabinetai/cabinet a composite score of 7.9 out of 10, placing it in the Silver 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 0.0 and never affects the composite score or tier. The risk label of 'low' 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 2; 386* repo is at production-grade maturity but the consumer SHOULD note that Cabinet is local-first + self-hosted by design -- there is no hosted tier in the open-source package; the consumer SHOULD optionally join the Cabinet Cloud waitlist (https://runcabinet.com/waitlist) if they want hosted; the consumer SHOULD note that markdown-on-disk means backups are file-level (git commits or filesystem snapshots).