@nreactive/next SEE LICENSE IN LICENSE 2 versions

@nreactive/next

npm Homepage

Next.js integration for @nreactive/core — App Router & Pages Router request context, server actions, and a React provider that catches client errors

Versions

SEE LICENSE IN LICENSE

License

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

nreactive

Keywords

nextjsreacterror-trackingnreactive

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:nuxt	AI (typosquat): Scoped @nreactive/next is a Next.js integration package, not a typosquat of nuxt.	ai	2026/04/29
typosquat	typosquat.levenshtein:jest	AI (typosquat): Levenshtein match to jest is coincidental; package is a Next.js integration under @nreactive scope.	ai	2026/04/29
typosquat	typosquat.levenshtein:knex	AI (typosquat): Levenshtein match to knex is coincidental; package is a Next.js integration under @nreactive scope.	ai	2026/04/29

Versions (showing 2 of 2)

Version	Deps	Published
0.2.0	0 / 9	2026-04-28
0.1.1	0 / 9	2026-04-27

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