Direct Telegram API#998
Open
Tom-V wants to merge 1 commit into
Open
Conversation
Tom-V
force-pushed
the
tomv/replace-telegram-api
branch
from
July 15, 2026 21:41
e061e21 to
746c5f8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR replaces the
node-telegram-bot-apidependency with a direct HTTP call usingaxios.Reason:
The
node-telegram-bot-apipackage currently has:requestandrequest-promiselibrariesIn our use case we only rely on a single function that essentially performs a simple Telegram API request. Introducing a full library for this adds unnecessary dependencies and security risks.
Solution:
Replace the library usage with a direct call to the Telegram Bot API using
axios. This removes the vulnerable dependency chain while keeping the functionality equivalent.