← Home

@trpc/next

npm Repository Homepage
46
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

kattjuliusmarminge

Keywords

tanstack-intent

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:nuxt AI (typosquat): @trpc/next is the canonical tRPC Next.js adapter, not a typosquat of nuxt. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Short name 'next' triggers false positives; established package with 484k downloads. ai
typosquat typosquat.levenshtein:knex AI (typosquat): Short name 'next' triggers false positives; established package with 484k downloads. ai

Versions (showing 46 of 46)

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

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

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

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-03, known maintainer) provenance

This version was published by a different npm account (juliusmarminge) than the most recent previously approved version (katt) on 2025-04-03, 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.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: katt → juliusmarminge (on 2025-03-28, known maintainer) provenance

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