@trpc/next
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 |
|---|---|---|---|---|
| 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 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 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 | |
| 10.45.4 | 0 / 16 | |
| 10.45.3 | 0 / 16 |
v11.17.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.16.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.15.2
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.15.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.15.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.14.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.14.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.4
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.3
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.2
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.13.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.12.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.12.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.11.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.10.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.9.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.8.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.8.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.7.2
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.7.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.7.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.5.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.5.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.4
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.3
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.2
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.4.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.1
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.3.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.2.0
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.4
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.3
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.1.2
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.45.4
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.45.3
2 findingsPackage name '@trpc/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.