Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for Logseq users who want agent help on their own knowledge base but do not want models blindly rewriting Markdown files or depending on a hosted notes service.
Who should use it
Who should skip it
Avoid running MarcoPorcellato/matryca-plumber in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
MarcoPorcellato/matryca-plumber is tracked by RepoRadar as a tool in the Knowledge Tools section. It was first seen on 2026-06-18 and last updated on 2026-06-18. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, MarcoPorcellato/matryca-plumber is strongest on workflow potential (9.4) and open-source/build quality (8.4) and weakest on setup ease (6.4) — 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 MarcoPorcellato/matryca-plumber a composite score of 8.3 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 73.0 and never affects the composite score or tier. The risk label of 'medium' 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 tool can edit Markdown-backed notes on disk, so it should start on a backed-up test vault before it touches material you cannot easily reconstruct; Enabling MCP mutation tools or background automation widens the write surface beyond read-only retrieval, so those paths belong on a trusted local machine; Local-first is a strength here, but operators still need to review how summaries, link healing, and imports affect the structure of an existing vault.