PackIt ⟡ Global

PackIt is the first plugin that...

• Has more than 1 fragment.
• Reaches more than 2MB of code (excluding strings, etc.).
• Consists of more than 2 programming languages.
• Uses ElyxCore.
• Uses the Cruel build system.
• Used the ElyxBuilder build system.
• Uses more than 1 native library.
• Uses Jetpack Compose.
• Uses a FULLY custom settings implementation.
• Uses a custom BottomSheet implementation.
• Uses custom icons (Jetpack Compose), not from the Telegram client.
• The first plugin that compiles as an Android application.
• Uses custom dialogs instead of the Telegram component.
• Probably a lot more that I didn't remember. And a lot of small details.

Forum | PackIt RU

Found the very first versions of PackIt: Click

Forum | PackIt RU

Slightly delayed due to a major update. For now, use the repositories from here.

Forum | PackIt RU

PackIt 0.1.1
Report a bug: GitHub Issues
Forum: PackitGround
How to create a repository: repo-doc

WHAT CHANGED

This update is entirely about polishing. We gathered your reports, went through them, and closed more than 20 fixes — from minor visual roughness to crashes that spoiled the experience for no reason.

Stickers now load noticeably faster and finally animate as intended. Plugin sending and inline popups have been tidied up, description formatting works consistently everywhere. The interface is neater: elements no longer overlap the navigation panel, and long tag lists no longer spread out.

Installation options:
From file
GitHub Releases

Forum | PackIt RU

Released snapshot PackIt (06.08.2026)
Changelog:

• Fixed an error when reporting a plugin from the catalog.
• Removed duplication of the install button.
• Fixed tag display.
• Plugin profile now opens even for incompatible app versions.
• GitLab now displays the repository owner instead of a link, also supporting organizations.
• Fixed plugin sharing via "Share".
• Fixed an error when suggesting a plugin to a repository.
• Restored formatting of translated plugin descriptions.
• Bullet points and buttons no longer overlap with the navigation panel.
• Fixed the position of the catalog button.
• Aligned the "Find" button text in AI search.
• Fixed the sticker on the native library error panel.
• Fixed rare crashes during ripple animations.
• Fixed plugin description formatting after translation.
• Improved sticker loading: Sticker loading is now faster, more reliable, and correctly supports animated stickers.
• Other minor fixes.

Download snapshot
What is a snapshot

Forum | PackIt RU

ATTENTION!

At the moment, the official PackIt repository is frozen for some technical reasons; its operation will be restored within a few days. If you have sent plugins, they will be published on the weekend.

Also, a bot for sending plugins to the PackIt repository will be available soon.

For now, you can use plugins from third-party repositories

Forum | PackIt RU

If you have your own PackIt repository, read this

Forum | PackIt RU

@homewatcha is also half a bet developer half a bet translator.

Forum | PackIt RU

Yesterday I was very busy, and today there was almost no time either. But I still managed to squeeze out a few minutes to write this post.

After 7.5 months of PackIt development and 368 days of work on ElyxCore, the first release of PackIt has arrived.

It is the largest project in exteraGram in terms of code volume and functionality, the most thoroughly worked out in terms of design, and undoubtedly the highest quality. Of course, it was not without bugs, unfinished parts, and various problems, as is typical for any first release. Moreover, for most of the journey, this project was created by only 2 developers and five testers. Closer to completion, several more developers joined us, and their help proved to be very important.

In general, initially PackIt was an unnamed plugin with text commands like .install plugin. Later, I met @mr_Vestr and proposed working on this project together. After some time, I came up with the name PackIt and somehow drew an icon.
Thanks to @mr_Vestr, the project gradually moved from text commands to a full-fledged interface. Over time, the commands were completely removed, and PackIt began to turn into a real application.
After some time, I began to study Android and Java properly. It was then that I got the opportunity to take on the project seriously: it ceased to be a simple text \"manager\" and became a full-fledged quality project.
Around the middle of development, testers joined the project: @red1k, @kaltsitu, @homewatcha, @djnore, @inlovewithumi, and @xarmaq, who was later removed due to inactivity.
Later, @ageekapple joined us. He didn't help particularly much, but still, a big thank you for supporting the project.
Right at the end of development, the team of developers was supplemented by 3 more people: @oodze and the returning developer @xarmaq worked on the Kotlin part of the project, while @larpcoup joined as a native developer (spoiler: in the end, he didn't write anything for the native part).

A separate and huge thank you to @pixwet. Throughout almost the entire development, he helped the project many times. Without him, this project would hardly have turned out exactly like this.

Every person I mentioned above contributed to PackIt. Someone wrote code, someone tested, someone helped with advice or ideas. And it is thanks to these people that the release became possible.
Thank you to everyone who was part of this project.

If I ever get around to it, I will definitely write the full history of the creation of PackIt and ElyxCore.

Forum | PackIt RU

Next week 0.1.1 will be released with fixes for all bugs that will be submitted this week.

Forum | PackIt RU

Updating non-working plugins, as well as adding new ones, will be done tonight.

You can send plugins in advance here: t.me/packitd/4

Forum | PackIt RU

How to install PackIt on the latest private beta version of AyuGram. (Not a release, and not exteraGram)

Click

Forum | PackIt RU

If you have a GitHub account and a few seconds of time, please star this: shareui/packit-source

Forum | PackIt RU

First release PackIt

To begin, update to the latest version of exteraGram. Then go here and update the SDK.

Report a bug: GitHub Issues
Forum: PackitGround
How to create a repository: repo-doc
WHERE TO SEND PLUGINS

All plugin functionality is located in its settings.

Installation options:
From file
GitHub Releases

The next private beta of exteraGram will be unobfuscated!

Forum | PackIt RU

Local plugin scanning in Packit

This function has become significantly better. I just heavily updated the plugin verification system. The scanner now analyzes not only the source code, but also many ways of hiding potentially dangerous actions.

What changed:

• Over 200 signatures for detecting suspicious code.
• Improved source code analysis.
• Support for composite signatures for more accurate threat detection.
• An exclusion system that reduces the number of false positives.
• Recognition of many common obfuscation and code hiding methods.
• Improved detection of dangerous functions even when attempts are made to mask their usage.
• Decryption and scanning of zlib, xor, base64, caesar, unicode escape, and so on.
• Detection of attempts to retrieve, read, or steal the API key used by Packit.

As a result, local verification has become noticeably more effective and capable of finding more potentially dangerous plugins before their installation. It is important to understand that no analyzer can guarantee 100% detection of any threats, however, the new scanner significantly increases the security level and allows for the identification of many suspicious plugins before launch.

After the release of ElyxCore, it is also planned to add analysis of Python bytecode based on pycdas; Decompilation and analysis of native libraries (.so) based on Ghidra; Decompilation and analysis of JVM components (.dex) based on Jadx; This will allow checking not only source code, but also compiled files.

Forum | PackIt RU

Proprietary source code and paid plugins

PackIt plans to adhere to a FOSS approach: the source code is open, any user can verify what a plugin does, and developers can freely study others' solutions and contribute to the community's development. However, the question arises: should the distribution of plugins with closed source code be allowed, including obfuscated builds, and should the restriction on paid plugins be removed?

On one hand, this would open up additional opportunities for developers. Some authors would be able to monetize their work, which could potentially lead to the emergence of larger and more functional projects. Furthermore, some developers are likely simply not ready to publish their work in an open format, but might be willing to release plugins in a closed format. On the other hand, closed source code inevitably reduces the level of transparency. The user can no longer independently verify exactly what the plugin does, what data it processes, and what actions it performs within the client. Even with moderation, there remains a certain level of trust required in the plugin author.

If this feature is added, such plugins will be clearly highlighted in the catalog. They will display a large warning stating that the source code is not available for verification and that usage is solely at the user's responsibility. Paid plugins will also have corresponding labeling. The question is: should closed and paid plugins be allowed, while maintaining user notification about potential risks, or is it better to continue adhering strictly to the FOSS philosophy and allow only fully open solutions?

Voting is available here.

Forum | PackIt RU

Stickers | Emoji