GitStar
⌘K
GitStar

A ranking dashboard for GitHub momentum, durable repository leaders, package adoption, and editorial context.

Data source · GitHub API and package ecosystem snapshots

Home

HomeTrendingMomentumPulseExplore

Discover

CategoriesLanguagesOrganizationsAI / MLMCP

Workflow

CompareWatchlistRandom

Knowledge

InsightGuideMethodology

Support

FAQAbout GitStarContactPrivacyTerms

© 2026 GitStar. All rights reserved.

Data sourced from GitHub API

TrendingMomentumPulseExplore
  1. Home
  2. Organizations
  3. Flame Engine
Flame EngineOrganization

Flame Engine

@flame-engine • 2D game engine built on top of Flutter. Maintained by https://github.com/bluefireteam. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.

Portfolio concentration

58%

Top three share

Shows whether the organization is driven by one breakout repo or several visible projects.

Breadth

29 repos

Visible snapshot

3 repositories updated in the last 90 days.

Leading language

Dart

Portfolio mix

Dart (20), Shell (7), HTML (1)

Average size

22

Stars per repository

Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.

Back to organizationsCompare repositories
Updated: 2026-05-17(118d ago)GitHub API fallback29 repositories

Portfolio Shape

58%

of the visible star count comes from this organization's top three repositories.

Average Repository Size

22

stars per repository in this same snapshot.

Current Mix

Dart

is the most common language here, with 3 repositories updated in the last 90 days.

Why this rank

This organization stands out because its public portfolio is relatively balanced across 29 repositories.

Balanced portfolio across 29 reposTop 3 share 58%

Organization pages work best when you separate portfolio breadth from flagship concentration. In Flame Engine's case, the visible top three repositories account for about 58% 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 Dart (20), Shell (7), HTML (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.

Source: GitHub API fallback. This is the same cache-first snapshot used by the organization ranking list, so the summary view and the detail view should stay aligned.

Top Repositories

#RepositoryLanguageStars🍴 ForksUpdated
1flame-engine/forge2d

A Dart port of Box2D

Dart203291 months ago
2flame-engine/oxygen

A lightweight Entity Component System written in Dart.

Dart102132 years ago
3flame-engine/gamepads

A Flutter plugin to handle gamepad input across multiple platforms.

Dart5934Today
4flame-engine/lightrunners

Flame game to showcase during https://fluttercon.dev/

Dart4112 years ago
5flame-engine/flame_forge2d

Package to add box2d support for the Flame game engine

Dart36125 years ago
6flame-engine/flame-bricks

Mason templates for the Flame Engine

Dart2425 years ago
7flame-engine/radiance

This library is a collection of AI algorithms used in games.

Dart2333 years ago
8flame-engine/space_shooter_workshop

This is the repository for the Space Shooter workshop.

Dart211010 months ago
9flame-engine/ignite-cli

Simple CLI interface for Ignite; scaffold and setup your Flame projects with ease

Dart2141 years ago
10flame-engine/flame_tiled

Package to add Tiled support for the Flame game engine

Dart18174 years ago
11flame-engine/defend_the_donutDart1611 years ago
12flame-engine/flame_example

[ARCHIVED] A set of small game examples showcasing all the features provided by the Flame Engine

Dart1215 years ago
13flame-engine/flame-docs-site

Scripts to deploy Flame's documentation as HTML using Sphinx

Shell8134 days ago
14flame-engine/flame_tutorials

Repository with a collection of tutorials for Flame

Dart825 years ago
15flame-engine/flappy_ember

A workshop for a basic flappy birds like game.

Dart733 years ago
16flame-engine/flame_rive

[WIP] Future place where all Rive related code will live

Shell623 years ago
17flame-engine/flame_audio

Audio capabilities and helpers for playing sounds, music and effects on Flame games

Dart655 years ago
18flame-engine/sokobros

Our reference game made during the Flame Game Jam 2026

Dart303 months ago
19flame-engine/flame-tutorials-siteShell304 years ago
20flame-engine/flame-format-action

Github action for code format validation

Shell313 years ago
21flame-engine/flamepad

An online Dart editor with support for console, web, and Flutter apps

Dart314 years ago
22flame-engine/burning-starsHTML205 years ago
23flame-engine/flamedeck

An app with great Flame Mini Games!

Dart103 years ago
24flame-engine/flame-analyze-action

An opinionated action that analyzes a Flutter project

Shell114 years ago
25flame-engine/flame-dartdoc-action

Opinionated Github action for validation DartDoc

Shell124 years ago
26flame-engine/flame_concurrent_mod_errorC++001 years ago
27flame-engine/flame_rc14_perfomance_issueDart004 years ago
28flame-engine/flame-test-action

An opinionated action that validates tests on a Flutter project

Shell005 years ago
29flame-engine/flamepad-services

The server backend for a web based interactive Dart service

Dart004 years ago

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.
Open flagship repoCompare repositoriesBack to organizations

Learn and methodology

Keep trust-building context reachable, but behind the first data read instead of ahead of it.
GuideMethodologyArticlesWeekly Digest

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.