protobufjs 8.x
Use protobufjs ^8.0.0 for runtime protobuf reflection, schema loading, message conversion, and binary encoding/decoding. Prefer the ordinary reflection API unless generated code is supplied by protobufjs-cli.
- For
protobufjs@8.8.0- Verified
- 2026-09-08, 2 examples executed
- Package
@modootoday/pmcp-protobufjs@8.0.0
What it covers
- What this package provides
- Common runtime workflow
- Build a schema with reflection
- Message lifecycle and binary encoding
- Generated code and the CLI
- Services
- Version-specific caution
- Not covered
One example from this skill
This is the skill's own text, not a summary of it. It runs: that is what verifying means here.
import assert from "node:assert/strict";
import protobuf from "protobufjs";
const AwesomeMessage = new protobuf.Type("AwesomeMessage")
.add(new protobuf.Field("awesomeField", 1, "string"));
const root = new protobuf.Root()
.define("awesomepackage")
.add(AwesomeMessage);
const MessageType = root.lookupType("awesomepackage.AwesomeMessage");
assert.equal(MessageType, AwesomeMessage);
const message = MessageType.create({ awesomeField: "hello" });
assert.equal(message.awesomeField, "hello");
What it did in the sandbox
Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.
Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.
Getting it
With a subscription:
npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-protobufjs
It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.