← Home

@connectrpc/connect-fastify

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

jdailey_buftstamm-buf

Versions (showing 8 of 8)

Version Deps Published
2.1.2 0 / 3
2.1.1 0 / 3
2.1.0 0 / 3
2.0.4 0 / 3
2.0.3 0 / 3
2.0.2 0 / 3
2.0.1 0 / 3
2.0.0 0 / 3

v2.0.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sayers-buf → srikrsna-buf (on 2025-02-26, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: srikrsna-buf → sayers-buf (on 2025-01-09, known maintainer) provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.