next-auth
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish-env metadata gap; no behavioral risk for this canonical package. | ai | |
| 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 |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.24.15 | 9 / 39 | |
| 4.24.14 | 9 / 39 | |
| 4.24.13 | 9 / 39 | |
| 4.24.12 | 9 / 39 |
v4.24.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: better-gustavo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.14
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: better-gustavo.
This version was published by a different npm account than previous versions on 2026-04-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.