← Home

@trpc/upgrade

npm Repository Homepage

Upgrade scripts for tRPC

44
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

kattjuliusmarminge

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): tRPC migrated to GitHub Actions CI/CD publishing; SLSA attestation confirms legitimate automated pipeline. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects release cadence of this utility package within the tRPC monorepo, not account takeover. ai

Versions (showing 44 of 44)

Version Deps Published
11.18.0 4 / 11
11.17.0 4 / 11
11.16.0 4 / 11
11.15.2 4 / 11
11.15.1 4 / 11
11.15.0 4 / 11
11.14.1 4 / 11
11.14.0 4 / 11
11.13.4 4 / 11
11.13.3 4 / 11
11.13.2 4 / 11
11.13.1 4 / 11
11.13.0 4 / 11
11.12.1 4 / 11
11.12.0 4 / 11
11.11.0 4 / 11
11.10.0 4 / 11
11.9.0 4 / 11
11.8.1 4 / 11
11.8.0 4 / 11
11.7.2 4 / 11
11.7.1 4 / 11
11.7.0 4 / 11
11.6.0 4 / 11
11.5.1 4 / 11
11.5.0 4 / 11
11.4.4 4 / 11
11.4.3 4 / 11
11.4.2 4 / 11
11.4.1 4 / 11
11.4.0 4 / 11
11.3.1 4 / 11
11.3.0 4 / 11
11.2.0 4 / 11
11.1.4 4 / 11
11.1.3 4 / 11
11.1.2 4 / 11
11.1.1 4 / 11
11.1.0 4 / 11
11.0.4 4 / 11
11.0.3 4 / 11
11.0.2 4 / 11
11.0.1 4 / 11
11.0.0 4 / 11

v11.1.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: katt → juliusmarminge (on 2025-04-29, known maintainer) provenance

This version was published by a different npm account (juliusmarminge) than the most recent previously approved version (katt) on 2025-04-29, but juliusmarminge 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.

v11.1.1

1 finding
LOW No provenance attestation provenance

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

v11.1.0

1 finding
LOW No provenance attestation provenance

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

v11.0.4

1 finding
LOW No provenance attestation provenance

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

v11.0.3

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: juliusmarminge → katt (on 2025-04-08, known maintainer) provenance

This version was published by a different npm account (katt) than the most recent previously approved version (juliusmarminge) on 2025-04-08, but katt 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.

v11.0.2

1 finding
LOW No provenance attestation provenance

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

v11.0.1

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.

v11.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.