@rivetkit/next-js
Next.js integration for RivetKit actors and client
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.pattern:next | AI (typosquat): Scoped @rivetkit package; legitimately integrates with Next.js, not impersonating it. | ai | |
| phantom-deps | phantom-dep:hono | AI (phantom-deps): hono is a declared runtime dependency used in config/build; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 2.3.10 | 3 / 5 | |
| 2.3.9 | 3 / 5 | |
| 2.3.8 | 3 / 5 | |
| 2.3.7 | 3 / 5 | |
| 2.3.6 | 3 / 5 | |
| 2.3.5 | 3 / 5 | |
| 2.3.4 | 3 / 5 | |
| 2.3.3 | 3 / 5 | |
| 2.3.2 | 3 / 5 | |
| 2.3.1 | 3 / 5 | |
| 2.3.0 | 3 / 5 | |
| 2.2.1 | 3 / 5 | |
| 2.2.0 | 3 / 5 | |
| 2.1.10 | 3 / 5 | |
| 2.1.9 | 3 / 5 | |
| 2.1.8 | 3 / 5 | |
| 2.1.7 | 3 / 4 | |
| 2.1.6 | 3 / 4 | |
| 2.1.5 | 3 / 4 | |
| 2.1.4 | 3 / 4 | |
| 2.1.3 | 3 / 4 | |
| 2.1.2 | 3 / 4 | |
| 2.1.1 | 3 / 4 | |
| 2.1.0 | 3 / 4 | |
| 2.0.42 | 3 / 4 | |
| 2.0.41 | 3 / 4 | |
| 2.0.40 | 3 / 4 | |
| 2.0.39 | 3 / 4 | |
| 2.0.38 | 3 / 4 | |
| 2.0.37 | 3 / 4 | |
| 2.0.36 | 3 / 4 | |
| 2.0.35 | 3 / 4 | |
| 2.0.34 | 3 / 4 | |
| 2.0.33 | 3 / 4 | |
| 2.0.32 | 3 / 4 | |
| 2.0.31 | 3 / 4 | |
| 2.0.30 | 3 / 4 | |
| 2.0.29 | 3 / 4 | |
| 2.0.28 | 3 / 4 | |
| 2.0.27 | 3 / 4 | |
| 2.0.26 | 3 / 4 | |
| 2.0.25 | 3 / 4 | |
| 2.0.24 | 3 / 4 | |
| 2.0.23 | 3 / 4 | |
| 2.0.22 | 3 / 4 | |
| 2.0.21 | 3 / 4 | |
| 2.0.20 | 3 / 4 | |
| 2.0.19 | 3 / 4 | |
| 2.0.18 | 3 / 4 | |
| 2.0.17 | 3 / 4 | |
| 2.0.16 | 3 / 4 |
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.