OrganizationTeam Amaze
@teamamaze • Dedicated team of devs working on Open Source mobile utility apps. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
99%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
13 repos
Visible snapshot
1 repositories updated in the last 90 days.
Leading language
Kotlin
Portfolio mix
Kotlin (5), Go (2), Unknown (1)
Average size
547
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2023-12-31(1030d ago)GitHub API fallback13 repositories
99%
of the visible star count comes from this organization's top three repositories.
547
stars per repository in this same snapshot.
Kotlin
is the most common language here, with 1 repositories updated in the last 90 days.
Why this rank
This organization stands out because one flagship repo drives 91% of its visible star count.
Flagship share 91%Breakout repo: AmazeFileManager
Organization pages work best when you separate portfolio breadth from flagship concentration. In Team Amaze's case, the visible top three repositories account for about 99% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Kotlin (5), Go (2), Unknown (1). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | teamamaze/AmazeFileManager Material design file manager for Android | Kotlin | 6.4K |
| 2 | teamamaze/AmazeFileUtilities An open source Google Files alternative for Android | Kotlin | 529 |
| 3 | teamamaze/LaputaCloudsLib Manage files in Google Drive, OneDrive, pDrive, Box, DropBox. Spiritual successor to CloudRail | Kotlin | 35 |
| 4 | teamamaze/FilePreloaderLibrary Loading takes time, catching takes space, preloading takes neither | Kotlin | 33 |
| 5 | teamamaze/AmazeFileUtilities-Issue-Tracker Issue tracker for Amaze File Utilities | 29 | |
| 6 | teamamaze/mupdf-android-viewer | Java | 11 |
| 7 | teamamaze/AmazeTrashBin | Kotlin | 9 |
| 8 | teamamaze/amaze-github-automation GitHub issue automation api function | Go | 8 |
| 9 | teamamaze/amaze-telegram-bot Bot for Amaze Telegram channel - https://t.me/AmazeFileManager | Python | 8 |
| 10 | teamamaze/opencv-android | C++ | 4 |
| 11 | teamamaze/amaze-crash-automation | Go | 3 |
| 12 | teamamaze/mupdf-android-fitz | C | 1 |
| 13 | teamamaze/ACRA-to-issue | JavaScript | 0 |
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.