Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI engineers and Apple-platform developers who want production LLM inference running entirely on the Apple Neural Engine — ane-book is the practitioner's guide with converters, Swift runtimes, and validated model manifests, and every model in the repo runs 100% on the ANE (verified with MLComputePlan, no GPU fallback, no CPU matmuls); for engineering teams that need to deploy LLMs on Ap
Who should use it
Who should skip it
Skip videlalvaro/ane-book if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
videlalvaro/ane-book is tracked by RepoRadar as a production llm inference on appl in the MIT practitioner's guide to production LLM infer section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Silver tier and moderate setup difficulty. videlalvaro/ane-book leads on novelty (9.0) and workflow potential (8.9); its lowest signal is maturity (6.3), so factor that in before investing setup time. 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 videlalvaro/ane-book 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 32.0 and never affects the composite score or tier. The risk label of 'none' 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
No inherent user-impacting risk is flagged from the captured evidence.
