@asyncflowstate/next
Next.js optimized integration for AsyncFlowState. Handle SSR, server actions, and app router transitions with declarative loading states.
Supply chain provenance
Status for the latest visible version.
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
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): Scoped @asyncflowstate/next is a Next.js integration, not a nuxt typosquat. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @asyncflowstate/next is a Next.js integration, not a jest typosquat. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped @asyncflowstate/next is a Next.js integration, not a knex typosquat. | ai |
v3.0.0
2 findingsPackage name '@asyncflowstate/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.
v2.0.2
2 findingsPackage name '@asyncflowstate/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.
v2.0.1
2 findingsPackage name '@asyncflowstate/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.
v2.0.0
2 findingsPackage name '@asyncflowstate/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.