An api for storing and retrieving decomp project progress 🐸
Go to file
Ethan Roseman defeb51bd9
Dep updates (#35)
* Dep updates

* black

* mypy
2023-12-18 18:49:51 +09:00
.github/workflows Dep updates (#35) 2023-12-18 18:49:51 +09:00
.vscode Dep updates (#35) 2023-12-18 18:49:51 +09:00
deployment Dep updates (#35) 2023-12-18 18:49:51 +09:00
frog_api Dep updates (#35) 2023-12-18 18:49:51 +09:00
frogress static r00t 2022-11-24 01:59:36 +09:00
.dockerignore Docker (#16) 2022-09-04 21:28:59 +09:00
.env Enhance support for docker-compose (#23) 2023-03-07 16:44:58 +09:00
.gitignore bye caddy 2022-11-22 00:11:12 +09:00 0.2.0: Fixes and improvements (#33) 2023-05-25 18:50:09 +09:00 Enhance support for docker-compose (#23) 2023-03-07 16:44:58 +09:00 0.2.0: Fixes and improvements (#33) 2023-05-25 18:50:09 +09:00
LICENSE 0.3.0: Bug-fixes & cleanup (#34) 2023-05-26 01:05:28 +09:00 Update diccord username 2023-11-09 17:08:50 +09:00
cli.ini Upgrade deps, cli beginnings, api reorg (#18) 2022-09-23 05:40:44 +09:00 0.2.0: Fixes and improvements (#33) 2023-05-25 18:50:09 +09:00
docker-compose.yaml Enhance support for docker-compose (#23) 2023-03-07 16:44:58 +09:00 CI (#6) 2022-08-25 12:41:19 +09:00
mypy.ini 0.2.0: Fixes and improvements (#33) 2023-05-25 18:50:09 +09:00
poetry.lock Dep updates (#35) 2023-12-18 18:49:51 +09:00
pyproject.toml Dep updates (#35) 2023-12-18 18:49:51 +09:00


An API for storing/retrieving decompilation progress


For those interested in contributing to frogress's development, please see


This project can be deployed locally using Docker Compose.

docker-compose up --build

See for more information.


The API is hosted at There are two main start routes: one for the structure of the data and one for the data itself.

Structure: projects/

Data: Structure: data/

In order to push data for a project, you will need a site admin to create a project for you in the database and give you the project slug and API key. Please reach out to me on Github, Discord (ethteck), or wherever, if you'd like to use Frogress for your project.

Read User Guide to learn more.

Database structure

In a nutshell, the db heirarchy goes project > version > category > entry > measure. The database is extremely flexible in that it allows you to organize your data however you want. That being said, there is a "standard" way of doing this that will be explained below.

Note: Any time a "slug" field is mentioned, this field is used as a url-friendly identifier. A slug for the "Bunny's Birthday Bonanza project" might be bbb, for example.


A project is a decompilation project, which would usually be tied to a GitHub repo and game.

slug: A slug for the project ("bbb")

name: Human-friendly name ("Bunny's Birthday Bonanza")

auth_key: The secret key used to push data to this project, given to you by a site admin

The following 3 fields are optional:

repository: A url to the git repository for this project

discord: A url to the discord server for this project

website: A url to the website for this project


Each project contains any number of versions.

slug: A slug for the version ("us")

name: Human-friendly name ("US 1.0")


Each version contains any number of categories. A category can represent anything you want, but the original idea was to allow for categories to represent parts of the project, such as different files being decompiled, different categories of data, etc. The reason we added this layer is that there are arguably different kinds of metrics one may track for different aspects of a project.

As an example, you could have a "documentation" category in which you estimate documentation % and track it in frogress. The documentation progress doesn't really align with the decompilation progress, so it makes sense to put it in a totally different bucket and have different entries associated with it.

If this extra layer isn't necessary for your project, feel free to just use one category.

slug: A slug for the category ("default", "actors", "documentation")

name: Human-friendly name

The above layers of the schema define the structure of the project in the database. Once you have an api key from a site admin, you can set this up yourself with The below two layers are created upon data insertion.


An entry represents a snapshot in time and is tied to a specific category. An entry holds a number of measures, which are bits of data.

timestamp: A unix timestamp associated with the entry, as an integer (12345) git_hash: The git commit hash that the entry is based upon ("af03bc")


Finally, we arrive at the actual data itself. Each measure has a type and value.

type: The type of the measure, as as string ("code", "code/total", "functions", "functions_total")

value: An integer representing the value of this measure (300, 10000)

Most projects use the "/" convention, so the current decompiled "code" bytes would have the "code" type, and the type for the total amount of decompilable code would be "code/total". However, the types can be named however you want. This may change later on.