AI marks

mautrix-telegram

Active stable

Puppeting and relay-bot bridge between Matrix and Telegram, rewritten in Go on mautrix-go bridgev2.

puppeting bridge · licence AGPL-3.0-or-later

Last commit
yesterday 3 Nov 2026
Commits, last year
401 62 in 90 days
Authors, 90 days
6 13 in a year, 57 ever
Bus factor
1 authors making half of last year's commits
Last release
v0.2610.0 16 Oct 2026 · 8 tags in a year
Lines of code
715k Go

AI

AI policy

What the project says about AI-made contributions

Restricted (fits the chosen stance)(against the chosen stance)
“In general, you can use AI to help with contributions. However, AI slop is not accepted. The author is accountable for the code. [...] AI should not be used for communicating with humans.”

Source: github.com/mautrix/docs/blob/da79465b14f6490d6f9a73d53ca5953d6cce0d75/bridges/general/contributing.md

AI in development

Whether the developers use AI tools on the repository

Occasional (fits the chosen stance)(against the chosen stance)

attributed share is below the rubric's 1 % line; shown as occasional because commits are attributed (lower bound)

Collector: 1 of 401 commits in the last year credit an AI tool (0.3 %): claude 1. 0 agent files, 0 AI workflows. A lower bound: most AI use leaves no trace.

  • 1 of 403 non-bot commits in the last 365 days (0.2 %) carry an AI co-author trailer or 'Generated with' line, e.g. https://github.com/mautrix/telegram/commit/b00e116ce527ec53b3053702bc141241a2de56ea
  • b00e116ce 2026-10-29 claude

AI in the product

Whether the product itself has AI features

None found (fits the chosen stance)(against the chosen stance)

no generative-AI features found in the README, ROADMAP or code

Activity

NovDecJanFebMarAprMayJunJulAugSeptOct MonWedFri
401 commits on 129 days in the last year · outlined: the day of the last collection
Nov: 0Nov: 2Nov: 2Nov: 19Dec: 31Dec: 35Dec: 8Dec: 4Jan: 1Jan: 1Jan: 3Jan: 1Jan: 0Feb: 4Feb: 1Feb: 0Feb: 13Mar: 2Mar: 15Mar: 9Mar: 59Apr: 22Apr: 25Apr: 6Apr: 12Apr: 16May: 12May: 2May: 6May: 3Jun: 0Jun: 12Jun: 3Jun: 0Jul: 2Jul: 1Jul: 6Jul: 0Jul: 1Aug: 1Aug: 3Aug: 9Aug: 3Sept: 1Sept: 5Sept: 4Sept: 2Oct: 5Oct: 9Oct: 3Oct: 8Oct: 9
Commits per week, last 52 weeks · peak 59 (Mar)
Commits per week, last 52 weeks
Nov0
Nov2
Nov2
Nov19
Dec31
Dec35
Dec8
Dec4
Jan1
Jan1
Jan3
Jan1
Jan0
Feb4
Feb1
Feb0
Feb13
Mar2
Mar15
Mar9
Mar59
Apr22
Apr25
Apr6
Apr12
Apr16
May12
May2
May6
May3
Jun0
Jun12
Jun3
Jun0
Jul2
Jul1
Jul6
Jul0
Jul1
Aug1
Aug3
Aug9
Aug3
Sept1
Sept5
Sept4
Sept2
Oct5
Oct9
Oct3
Oct8
Oct9
2023 Q1: 22023 Q2: 62023 Q3: 22023 Q4: 22024 Q1: 22024 Q2: 32024 Q3: 32024 Q4: 42025 Q1: 22025 Q2: 52025 Q3: 52025 Q4: 62026 Q1: 32026 Q2: 52026 Q3: 52026 Q4: 5
Authors per quarter · peak 6 (2023 Q2)
Authors per quarter
2023 Q12
2023 Q26
2023 Q32
2023 Q42
2024 Q12
2024 Q23
2024 Q33
2024 Q44
2025 Q12
2025 Q25
2025 Q35
2025 Q46
2026 Q13
2026 Q25
2026 Q35
2026 Q45

Languages

  • Go98.5 %
  • TL1.2 %
  • Go Template0.2 %
by lines of code (scc)

Features

FeatureValueHow we knowEvidence
Network Telegram — —
Framework yes
mautrix-go bridgev2
code github.com/mautrix/telegram/blob/f7bb767679114f0
Puppeting yes
double puppeting (automatic via an appservice registration, or manual login); relay mode: https://github.com/mautrix/docs/blob/da79465b14f6490d6f9a73d53ca5953d6cce0d75/bridges/general/relay-mode.md
claimed github.com/mautrix/docs/blob/da79465b14f6490d6f9
Encryption (E2EE) Yes: Yes
optional end-to-bridge encryption of the Matrix side (Matrix rooms encrypted between users and the bridge)
claimed github.com/mautrix/docs/blob/da79465b14f6490d6f9
Backfill Yes: Yes code github.com/mautrix/telegram/blob/f7bb767679114f0
Media Yes: Yes
files and media; polls, games and buttons not bridged
claimed github.com/mautrix/telegram/blob/f7bb767679114f0
Reactions and edits Yes: Yes claimed github.com/mautrix/telegram/blob/f7bb767679114f0
Group chats Yes: Yes
groups, supergroups and channels
claimed github.com/mautrix/telegram/blob/f7bb767679114f0
Login methods yes
phone number + code (and 2FA password), QR code, or a bot token for relaying
claimed github.com/mautrix/docs/blob/da79465b14f6490d6f9
Terms-of-service risk partial
"Telegram is known to ban suspicious users, and a brand new account using a 3rd party client is considered suspicious. Using a well-established account is perfectly safe."
claimed github.com/mautrix/docs/blob/da79465b14f6490d6f9

Health signals

Bus factor (last year)
1
Issue first response
not measured (the forge did not give it)
Release cadence
8 tags in the last year, latest v0.2610.0 (16 Oct 2026)
CI
.github/workflows/go.yml .github/workflows/stale.yml .gitlab-ci.yml
Tests
test files found
Security policy
none found
Licence
AGPL-3.0-or-later
Funding
github.com/sponsors/tulir
Telemetry SDKs in manifests
Segment (go.mod)

Repositories

RepositoryRoleActivityLast commitCommits 1yAuthors 90dMeasured at
github.com/mautrix/telegram main Active 3 Nov 2026 401 6 f7bb76767

Notes

matrix.org still lists it as Python/Beta; the repo's CHANGELOG.md says the bridge was rewritten in Go on bridgev2, and v26.10 dropped migration from the Python version. Other Telegram bridges: matrix-appservice-telegram (FruitieX, abandoned).

Researched by an AI agent (Claude) on 5 Nov 2026, not checked by a person; metrics collected on 5 Nov 2026. Source file: data/projects/bridge/mautrix-telegram.yaml. Spotted a mistake? Open an issue with a link.