@bufbuild/protoplugin
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from individual maintainer to GitHub Actions CI/CD with SLSA provenance; expected for bufbuild org. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.13.0 | 3 / 0 | |
| 2.12.1 | 3 / 0 | |
| 2.12.0 | 3 / 0 | |
| 2.11.0 | 3 / 0 | |
| 2.10.2 | 3 / 0 | |
| 2.10.1 | 3 / 0 | |
| 2.10.0 | 3 / 0 | |
| 2.9.0 | 3 / 0 | |
| 2.8.0 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.3 | 3 / 0 | |
| 2.6.2 | 3 / 0 | |
| 2.6.1 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.2 | 3 / 0 | |
| 2.5.1 | 3 / 0 | |
| 2.5.0 | 3 / 1 | |
| 2.4.0 | 3 / 1 | |
| 2.3.0 | 3 / 1 | |
| 2.2.5 | 3 / 1 | |
| 2.2.4 | 3 / 1 | |
| 2.2.3 | 3 / 1 | |
| 2.2.2 | 3 / 1 | |
| 2.2.1 | 3 / 1 | |
| 2.2.0 | 3 / 1 | |
| 2.1.0 | 3 / 1 | |
| 2.0.0 | 3 / 1 |
v2.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tstamm-buf) than the most recent previously approved version (sayers-buf) on 2024-12-09, but tstamm-buf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tstamm-buf) than the most recent previously approved version (sayers-buf) on 2024-11-01, but tstamm-buf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (sayers-buf) than the most recent previously approved version (tstamm-buf) on 2024-10-28, but sayers-buf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (srikrsna-buf) than the most recent previously approved version (tstamm-buf) on 2024-10-08, but srikrsna-buf is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.