Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for product teams shipping on the Vercel AI SDK who need to see model cost, timing, and failure behavior without building their own prompt telemetry stack from scratch.
Who should use it
Who should skip it
Consider foglamp-labs/foglamp lower priority if you already have a working solution in this category.
About this signal
foglamp-labs/foglamp is tracked by RepoRadar as a sdk telemetry in the Evaluation and Observability section. It was first seen on 2026-06-29 and last updated on 2026-06-29. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. foglamp-labs/foglamp leads on open-source/build quality (8.4) and workflow potential (8.2); its lowest signal is momentum (4.0), 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 foglamp-labs/foglamp 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
Prompt and response traces can capture sensitive user inputs and model output, so self-host or lock down the telemetry store before pointing production traffic at it; The quick-start path uses a hosted endpoint and API key, so validate retention, redaction, and access controls before broader rollout.