Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI-coding-agent teams who want a 'no server, no database, no daemon' shared-experience substrate (just git clone + python3 search_knowledge.py) so a fix one agent finds for a recurring failure (pip on WSL, ChromaDB on NTFS, FANUC error codes, etc.) is searchable by every other agent on the team without standing up a vector store or a hosted knowledge service; for zero-dep Python
Where this stands now
Ikalus1988/MisakaNet ranks #636 of 2304 tracked Radar items by composite score (7.9 against a section median of 5.2). The section currently carries 1197 Bronze, 645 Gold, 462 Silver. RepoRadar has retained observations for this record since 2026-06-24 (95 days in the current window). Signal extremes versus the section: momentum at the 97th percentile; novelty at the 97th percentile.
Who should use it
Who should skip it
Skip Ikalus1988/MisakaNet unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
Ikalus1988/MisakaNet is tracked by RepoRadar as an AI project in the Radar section. First seen 2026-06-24; the source record was last checked on 2026-06-24. The current verdict is 'try now' with a Silver tier and review needed setup difficulty. The standout signals for Ikalus1988/MisakaNet are novelty (10.0) and momentum (10.0), while setup ease (6.5) trails — that balance shapes where it fits best. 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 Ikalus1988/MisakaNet record combines a 7.9/10 composite score with separate popularity (100.0), risk (low), and setup (review needed) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
Risk label is still being reviewed from the captured evidence. Treat the item as unknown-risk until you review the linked source, permissions, setup path, and data access.