Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for security and IT teams that need visibility into AI agent activity across local endpoints, CI jobs, and cloud-agent surfaces: Agent Beacon is the MIT open-source telemetry layer that extends the OpenTelemetry GenAI standard and normalizes runtime events into a unified data model; for security operations centers that already run an OpenTelemetry pipeline and want AI agent activity to feed
Who should use it
Who should skip it
Skip Asymptote-Labs/agent-beacon if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
Asymptote-Labs/agent-beacon is tracked by RepoRadar as a open-source opentelemetry genai in the MIT open-source telemetry layer for AI agents th section. It was first seen on 2026-06-25 and last updated on 2026-06-25. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, Asymptote-Labs/agent-beacon is strongest on workflow potential (9.7) and novelty (9.0) 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 Asymptote-Labs/agent-beacon a composite score of 8.2 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 262.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
**Default local-only processing; SIEM forwarding is opt-in and the redaction layer is the security boundary.** The default posture is local-only — events are processed and inspected on the endpoint and never leave the host. SIEM forwarding is opt-in and the redaction layer (which can strip prompt text, response text, file paths) is the security boundary between what the team inspects locally and what the SIEM sees. Adopters must configure the redaction settings deliberately before forwarding to a SIEM — a misconfigured redaction layer can leak prompt content (which often contains source code, credentials, or PII) to the SIEM. Run the redaction config through a security review before enabling SIEM forwarding; **Detection rules in `rules/` are a starting set; adapt to the team's threat model before relying on them.** The detection rules shipped in `rules/` are a starting set for suspicious agent activity (e.g. agent access to credential files, agent egress to non-allowlisted domains, agent modifications to system paths). They are not a turnkey detection suite — security engineers should review, extend, and tune them to the team's threat model before relying on them as the primary detection layer. Run a tabletop exercise to confirm the rules fire on the agent activity the team actually cares about; **AI-assisted development surface (17KB CLAUDE.md) is intentional; review the agent surface for sensitive operations.** The repository ships a 17KB CLAUDE.md so AI-assisted development (Claude Code, Codex, etc.) can contribute to the project. Adopters running Beacon in production should be aware that the CLAUDE.md instructs the agent on the project's architecture and conventions; this is a development convenience, not a production risk, but security-conscious teams should review the CLAUDE.md before any AI agent operates on the Beacon codebase in a production-trusted environment.