@rivetkit/next-js Apache-2.0 56 versions

@rivetkit/next-js

npm

Next.js integration for RivetKit actors and client

56

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

nathanflurryanticipate-brave-cookies

Keywords

rivetkitnextjsnextnextjs-frameworknext-jsreactframeworkwebserverlessedgeactormicroservices

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	2026/05/23
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	2026/05/23

Versions (showing 56 of 56)

Version	Deps	Published
2.2.1	3 / 5	2026-04-02
2.2.0	3 / 5	2026-03-31
2.1.10	3 / 5	2026-03-26
2.1.9	3 / 5	2026-03-26
2.1.8	3 / 5	2026-03-26
2.1.7	3 / 4	2026-03-23
2.1.6	3 / 4	2026-03-04
2.1.5	3 / 4	2026-03-03
2.1.4	3 / 4	2026-03-03
2.1.3	3 / 4	2026-02-26
2.1.2	3 / 4	2026-02-26
2.1.1	3 / 4	2026-02-24
2.1.0	3 / 4	2026-02-24
2.0.42	3 / 4	2026-01-26
2.0.41	3 / 4	2026-01-23
2.0.40	3 / 4	2026-01-22
2.0.39	3 / 4	2026-01-21
2.0.38	3 / 4	2026-01-15
2.0.37	3 / 4	2026-01-14
2.0.36	3 / 4	2026-01-14
2.0.35	3 / 4	2026-01-13
2.0.34	3 / 4	2026-01-13
2.0.33	3 / 4	2025-12-31
2.0.32	3 / 4	2025-12-29
2.0.31	3 / 4	2025-12-28
2.0.30	3 / 4	2025-12-27
2.0.29	3 / 4	2025-12-20
2.0.28	3 / 4	2025-12-15
2.0.27	3 / 4	2025-12-12
2.0.26	3 / 4	2025-12-12
2.0.25	3 / 4	2025-12-02
2.0.24	3 / 4	2025-11-21
2.0.23	3 / 4	2025-11-06
2.0.22	3 / 4	2025-11-05
2.0.21	3 / 4	2025-10-26
2.0.20	3 / 4	2025-10-20
2.0.19	3 / 4	2025-10-20
2.0.18	3 / 4	2025-10-18
2.0.17	3 / 4	2025-10-17
2.0.16	3 / 4	2025-10-15
2.0.15	3 / 4	2025-10-15
2.0.14	3 / 4	2025-10-13
2.0.13	3 / 4	2025-10-09
2.0.12	3 / 4	2025-10-09
2.0.11	3 / 4	2025-10-09
2.0.10	3 / 4	2025-10-07
2.0.9	3 / 4	2025-10-02
2.0.8	3 / 4	2025-10-01
2.0.7	3 / 4	2025-09-27
2.0.6	3 / 4	2025-09-18
2.0.5	3 / 4	2025-09-17
2.0.4	3 / 4	2025-09-16
2.0.3	3 / 4	2025-09-12
2.0.2	3 / 4	2025-09-05
2.0.1	3 / 4	2025-09-02
2.0.0	3 / 4	2025-09-02

v2.2.0

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.10

1 finding

LOW No provenance attestation provenance

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

v2.1.9

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.8

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.7

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.6

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.3

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.0

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.42

1 finding

LOW No provenance attestation provenance

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

v2.0.41

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.40

1 finding

LOW No provenance attestation provenance

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

v2.0.39

1 finding

LOW No provenance attestation provenance

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

v2.0.38

1 finding

LOW No provenance attestation provenance

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

v2.0.37

1 finding

LOW No provenance attestation provenance

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

v2.0.36

1 finding

LOW No provenance attestation provenance

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

v2.0.35

1 finding

LOW No provenance attestation provenance

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

v2.0.34

1 finding

LOW No provenance attestation provenance

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

v2.0.33

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.32

1 finding

LOW No provenance attestation provenance

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

v2.0.31

1 finding

LOW No provenance attestation provenance

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

v2.0.30

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.29

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.28

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.27

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.26

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.25

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.24

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.23

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.22

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

v2.0.21

1 finding

LOW No provenance attestation provenance

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

v2.0.20

1 finding

LOW No provenance attestation provenance

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

v2.0.19

1 finding

LOW No provenance attestation provenance

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

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.17

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

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.

v2.0.1

2 findings

HIGH typosquat.pattern: Suspicious name similarity to 'next' typosquat

Package name '@rivetkit/next-js' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'next'.

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.

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.