Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who like coding agents but are tired of losing project memory, invariants, and roadmap context every time a session starts fresh.
Who should use it
Who should skip it
Pass on ngocquang/source-of-truth if its scope or audience does not match what your team is building right now.
About this signal
ngocquang/source-of-truth is tracked by RepoRadar as a plugin in the Developer Tools section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, ngocquang/source-of-truth is strongest on workflow potential (9.3) and open-source/build quality (8.4) and weakest on momentum (4.0) — 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 ngocquang/source-of-truth a composite score of 7.8 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 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It can generate and update project docs and sync them alongside commits, so review its catalog writes before letting it run unattended on a shared repository; The workflow treats your PRD or design docs as the upstream authority, so weak or stale source docs will propagate weak guardrails into the skill output.