esengine has not been fully verified yet. No recorded run has produced a verdict yet.

How did Argusic test esengine?

On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.

Where is the evidence for esengine?

All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

esengine

ESEngine - High-performance TypeScript ECS Framework for Game Development

Not yet testedsource: GitHub homepageTypeScriptMITcommit 2886284e8015

TypeScript, MIT licensed. The project labels itself: 2d game engine, behavior tree, ecs, entity component system, esengine, game development, game engine and game framework.

esengine has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict: Not yet tested
Argusic Score: not scored yet
recorded runs: 0
last tested: -
stars: 922
forks: 159
open issues: 0
watchers: 18
size: 65 MB
created: 2020-06-08
last push: 2026-07-30

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-08. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

2d-game-engine behavior-tree ecs entity-component-system esengine game-development game-engine game-framework physics sprite tilemap typescript wasm webgl

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/esengine.svg)](https://argusic.com/subject/esengine)

Questions

Does esengine run?: esengine has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test esengine?: On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for esengine?: All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.