Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who are tired of recreating prompts, hooks, skills, and long-term memory every time they move between coding-agent tools.
Who should use it
Who should skip it
Move on from codejunkie99/agentic-stack if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
codejunkie99/agentic-stack is tracked by RepoRadar as a framework 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 Gold tier and moderate setup difficulty. The standout signals for codejunkie99/agentic-stack are workflow potential (9.9) and practical usefulness (9.0), while setup ease (6.4) 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 codejunkie99/agentic-stack a composite score of 8.4 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 3.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 vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The installer writes hooks, config, and memory surfaces into multiple local agent environments, so review what it changes before pointing it at a production workspace; Its shared brain and dashboard can aggregate sensitive repo context, so keep secrets and regulated codebases out of early pilots until the data flow is clear; Upgrade commands should be tested with the dry-run path first because the value proposition depends on modifying live agent setups safely.