Hmm... there's Python and CPP.

  src/socketify
  ├── __init__.py
  ├── __main__.py
  ├── asgi.py
  ├── cli.py
  ├── helpers.py
  ├── libsocketify_darwin_amd64.so
  ├── libsocketify_darwin_arm64.so
  ├── libsocketify_linux_amd64.so
  ├── libsocketify_windows_amd64.dll
  ├── loop.py
  ├── native
  │  ├── Make.bat
  │  ├── Makefile
  │  ├── src
  │  │  ├── libsocketify.cpp
  │  │  └── libsocketify.h
  │  └── uv_selector.txt
  ├── native.py
  ├── socketify.py
  ├── ssgi.py
  ├── status_codes.py
  ├── tasks.py
  ├── uv.py
  ├── uWebSockets
  └── wsgi.py

I think the .so files are built from other source though? I'm not sure. In the makefile they are rm'd and then created. The linux workflow file, for example, has:

  make linux
  cd ../
  git add libsocketify_linux_amd64.so

Ah, thanks! In my defense, the native/ directory contains the portable C++ source and the src/ directory contains a the native executables.

Yes you are right!

you need to pull all git submodules too git submodule update --init --recursive --remote

Navigate down another directory to `native` directory which has the source for the .so files.

.so are the pre-built binaries but you can see the native folder code there and also see the projects used in Makefile