@connectrpc/connect
Supply chain provenance
Status for the latest visible version.
Maintainers
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 human publisher to GitHub Actions CI with SLSA provenance; expected for this org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org housekeeping; package has SLSA provenance and is under official connectrpc GitHub org. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.1.2 | 0 / 4 | |
| 2.1.1 | 0 / 4 | |
| 2.1.0 | 0 / 4 | |
| 2.0.4 | 0 / 4 | |
| 2.0.3 | 0 / 4 | |
| 2.0.2 | 0 / 4 | |
| 2.0.1 | 0 / 4 | |
| 2.0.0 | 0 / 4 |
v2.0.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 (srikrsna-buf) than the most recent previously approved version (sayers-buf) on 2025-02-26, 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.0.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 (srikrsna-buf) on 2025-01-09, 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.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.