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

How did Argusic test usagi?

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 usagi?

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.

usagi

A simple 2D game engine for rapid prototyping with Lua, featuring live reload and cross-platform export; this repo is a mirror and development happens at: https://codeberg.org/brettchalupa/usagi

Not yet testedsource: GitHub homepageRustUnlicensecommit a0a91abe5659

Rust, Unlicense licensed. The project labels itself: game development, game engine, game engine 2d, love2d, lua, pico 8, rust game dev and usagi engine.

usagi 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: 858
forks: 41
open issues: 0
watchers: 9
size: 5 MB
created: 2026-04-24
last push: 2026-10-05

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)

game-development game-engine game-engine-2d love2d lua pico-8 rust-game-dev usagi-engine

Embed the badge

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

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

Questions

Does usagi run?: usagi has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test usagi?: 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 usagi?: 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.