google-proto-files

All of the Google API's protocol buffer files

google-proto-files@6.1.0 was published on 2026-10-12. Its manifest declares 2 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=22.

All google-proto-files versions · Permanent reference to 6.1.0

Package specifications

Version6.1.0
License declarationApache-2.0
Published2026-10-12T22:24:54.407Z
Node.js requirement>=22
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size64437.74 KiB
Published file count6505
Package typeNot declared
ES module entryNot declared
Default entry./build/src/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies14
Repository stars3210
Repository forks724

Install google-proto-files 6.1.0

npm install google-proto-files@6.1.0
pnpm add google-proto-files@6.1.0
yarn add google-proto-files@6.1.0

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.

Code-Review10/10 — all changesets reviewed
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy10/10 — security policy file detected
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
License10/10 — license file detected
SAST7/10 — SAST tool detected but not run on all commits
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Fuzzing0/10 — project is not fuzzed

Evidence and freshness