@apollo/usage-reporting-protobuf

Protobuf format for Apollo usage reporting

@apollo/usage-reporting-protobuf@4.1.2 was published on 2026-05-04. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @apollo/usage-reporting-protobuf versions · Permanent reference to 4.1.2

Package specifications

Version4.1.2
License declarationMIT
Published2026-05-04T16:35:41.301Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size991.82 KiB
Published file count10
Package typemodule
ES module entrygenerated/esm/protobuf.js
Default entrygenerated/cjs/protobuf.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies13
Repository stars13954
Repository forks2001

Install @apollo/usage-reporting-protobuf 4.1.2

npm install @apollo/usage-reporting-protobuf@4.1.2
pnpm add @apollo/usage-reporting-protobuf@4.1.2
yarn add @apollo/usage-reporting-protobuf@4.1.2

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained2/10 — 1 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 2
Code-Review3/10 — Found 8/21 approved changesets -- score normalized to 3
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions9/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness