npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

protobuf-c-dump

v1.0.0

Published

Recover a .proto schema from a protobuf-c binary by walking its descriptor structs.

Readme

protobuf-c-dump

pipeline status npm version

Recover a .proto schema from a binary built with protobuf-c.

Most "dump the protobuf definitions from a binary" tools look for the serialized FileDescriptorProto that Google's protoc embeds in C++/Java/etc. output. protobuf-c doesn't emit that — it generates C descriptor structs (ProtobufCMessageDescriptor / ProtobufCEnumDescriptor). This tool walks those structs instead, so it works on protobuf-c binaries the protoc-oriented tools can't read.

How it works

For each <name>__descriptor symbol in the binary, the struct's magic word identifies it as a message or enum descriptor; the tool reads the message/field /enum names, field numbers, labels, and scalar/message/enum types straight out of the structs, resolving the position-independent pointers via the binary's RELATIVE relocations.

Install

npm install -g protobuf-c-dump   # or: npx protobuf-c-dump <file>

Usage

protobuf-c-dump libexample.so          # print recovered .proto
protobuf-c-dump libexample.so --json   # print the parsed schema as JSON

As a library:

import { readFileSync } from "fs";
import { extractSchema, renderProto } from "protobuf-c-dump";

const schema = extractSchema(readFileSync("libexample.so"));
console.log(renderProto(schema));

Limitations

  • 64-bit ELF only (.so, .o, executables) — not Mach-O or PE, not 32-bit.
  • Needs symbols. Descriptors are found via *__descriptor symbols; a fully stripped binary has none to follow.
  • Reconstruction, not the original. protobuf-c descriptors preserve names, field numbers, labels, and types, but not nesting, oneofs, maps, options, or comments — so the output is faithful but flattened.

Development

npm install
npm test              # jest (unit tests + a gated protoc-c integration test)
npm run typecheck     # tsc, strict
npm run build         # tsc → dist/
npm start -- <file>   # run the CLI from source (tsx)

The integration test compiles a real .proto with protoc-c and extracts from the result; it runs on Linux when protoc-c and a C compiler are present, and is skipped otherwise (the unit tests synthesize real ELF fixtures, so the pipeline is covered everywhere).

AI disclosure

This project was created with the help of AI — specifically Anthropic's Claude via Claude Code. That includes the code, tests, CI configuration, and documentation, with design decisions and validation made by a human. See AGENTS.md for the conventions AI contributors are expected to follow.

License

MIT