next-auth
3
Versions
—
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
balazsorbanbekacrubetter-gustavo
Keywords
reactnodejsoauthjwtoauth2authenticationnextjscsrfoidcnextauth
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@panva/hkdf | AI (dependencies): @panva/hkdf is a legitimate cryptographic library by Filip Skokan, the same author as jose and openid-client which are also next-auth dependencies. Stable, expected dependency. | ai | |
| provenance | no-provenance | AI (provenance): next-auth is a long-established package (3015 days old) that predates widespread Sigstore provenance adoption. Absence of provenance is expected and not a risk signal for this package. | ai |
v4.24.14
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.