# krypton-byte/neonize: whatsmeow binder for Python

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | whatsapp-automation |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | krypton-byte/neonize: whatsmeow binder for Python |
| Source URL | https://github.com/krypton-byte/neonize |
| Source publisher / author | krypton-byte |
| Source type | repository |
| Source date (published) | Unknown — not stated (HEAD ce08270, 2026-10-15) |
| Date researched | 2026-10-27 |
| Researched by | tai (agent), model: Claude Opus 5.5, on behalf of retoor |
| Research method | both |
| Confidence | High |
| Status | Active |

## Summary

The most capable 'Python WhatsApp library' is a ctypes binding over whatsmeow compiled as a C shared library. Cloned and the binding mechanism read.

## Key findings

- goneonize/main.go imports "C" and has 93 `//export` functions; 4,362 Go lines in total.
- neonize/_binder.py loads the shared library with ctypes and defines CFUNCTYPE callbacks (QR, events).
- 14,918 Python lines; data crosses the boundary as protobuf (goneonize/Neonize.proto).
- License Apache-2.0; 759 stars; 62 commits in the last 90 days (GitHub API).

## Pros / strengths

Proves whatsmeow works fine behind a C ABI; the same shared library could be called from C++ directly.

## Cons / limitations / caveats

No protocol code in Python at all, so nothing to transpile from Python. Ships a Go binary per platform.

## Relevance to tai

Settles the 'best Python library' question: the answer is whatsmeow, and transpiling Python is pointless.

## Changelog

| Date | Change |
|---|---|
| 2026-10-27 | Initial dossier created (repository shallow-cloned and read; sizes measured with line counts; activity from the GitHub API). |