← Home

@bufbuild/protoc-gen-es

npm Repository Homepage
26
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

bufdevtstamm-bufbufbotjdailey_bufdoriakeung

Keywords

protobufschematypescriptecmascriptprotoc-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/cjs/src/gen/minimal-validate_pb.js AI (source-diff): Base64-encoded protobuf file descriptor; standard codegen output for @bufbuild packages. ai

Versions (showing 26 of 26)

Version Deps Published
2.13.0 2 / 1
2.12.1 2 / 1
2.12.0 2 / 1
2.11.0 2 / 1
2.10.1 2 / 1
2.10.0 2 / 1
2.9.0 2 / 1
2.8.0 2 / 1
2.7.0 2 / 1
2.6.3 2 / 1
2.6.2 2 / 1
2.6.1 2 / 1
2.6.0 2 / 1
2.5.2 2 / 1
2.5.1 2 / 1
2.5.0 2 / 1
2.4.0 2 / 0
2.3.0 2 / 0
2.2.5 2 / 0
2.2.4 2 / 0
2.2.3 2 / 0
2.2.2 2 / 0
2.2.1 2 / 0
2.2.0 2 / 0
2.1.0 2 / 0
2.0.0 2 / 0

v2.13.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.12.1

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: tstamm-buf → GitHub Actions (on 2026-06-22, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (tstamm-buf) on 2026-06-22, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.