@descope/nextjs-sdk
Descope NextJS SDK
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@descope/core-js-sdk | AI (phantom-deps): Same-org monorepo dep; declared as transitive/peer, not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@descope/web-component | AI (phantom-deps): Same-org monorepo dep; bundled indirectly via react-sdk, phantom flag is a stable false positive. | ai |
Versions (showing 100 of 234)
| Version | Deps | Published |
|---|---|---|
| 0.14.11 | 4 / 59 | |
| 0.14.10 | 4 / 59 | |
| 0.14.9 | 4 / 59 | |
| 0.14.8 | 4 / 59 | |
| 0.14.7 | 4 / 59 | |
| 0.14.6 | 4 / 59 | |
| 0.14.5 | 4 / 59 | |
| 0.14.4 | 4 / 59 | |
| 0.14.3 | 4 / 59 | |
| 0.14.2 | 4 / 59 | |
| 0.14.1 | 4 / 59 | |
| 0.14.0 | 4 / 59 | |
| 0.13.20 | 4 / 59 | |
| 0.13.19 | 4 / 59 | |
| 0.13.18 | 4 / 59 | |
| 0.13.17 | 4 / 59 | |
| 0.13.16 | 4 / 59 | |
| 0.13.15 | 4 / 59 | |
| 0.13.14 | 4 / 59 | |
| 0.13.13 | 4 / 59 | |
| 0.13.12 | 4 / 59 | |
| 0.13.11 | 4 / 59 | |
| 0.13.10 | 4 / 59 | |
| 0.13.9 | 4 / 59 | |
| 0.13.8 | 4 / 59 | |
| 0.13.7 | 4 / 59 | |
| 0.13.6 | 4 / 59 | |
| 0.13.5 | 4 / 59 | |
| 0.13.4 | 4 / 59 | |
| 0.13.3 | 4 / 59 | |
| 0.13.2 | 4 / 59 | |
| 0.13.1 | 4 / 59 | |
| 0.13.0 | 4 / 59 | |
| 0.12.16 | 4 / 59 | |
| 0.12.15 | 4 / 59 | |
| 0.12.14 | 4 / 59 | |
| 0.12.13 | 4 / 59 | |
| 0.12.12 | 4 / 59 | |
| 0.12.11 | 4 / 59 | |
| 0.12.10 | 4 / 59 | |
| 0.12.9 | 4 / 59 | |
| 0.12.8 | 4 / 59 | |
| 0.12.7 | 4 / 59 | |
| 0.12.6 | 4 / 59 | |
| 0.12.5 | 4 / 59 | |
| 0.12.4 | 4 / 59 | |
| 0.12.3 | 4 / 59 | |
| 0.12.2 | 4 / 59 | |
| 0.12.1 | 4 / 59 | |
| 0.12.0 | 4 / 59 | |
| 0.11.6 | 4 / 59 | |
| 0.11.5 | 4 / 59 | |
| 0.11.4 | 4 / 59 | |
| 0.11.3 | 4 / 59 | |
| 0.11.2 | 4 / 59 | |
| 0.11.1 | 4 / 59 | |
| 0.11.0 | 4 / 59 | |
| 0.10.0 | 4 / 59 | |
| 0.9.0 | 4 / 59 | |
| 0.8.1 | 4 / 59 | |
| 0.8.0 | 4 / 59 | |
| 0.7.1 | 4 / 59 | |
| 0.7.0 | 4 / 59 | |
| 0.6.1 | 4 / 59 | |
| 0.6.0 | 4 / 59 | |
| 0.5.2 | 4 / 59 | |
| 0.5.1 | 4 / 59 | |
| 0.5.0 | 5 / 59 | |
| 0.4.0 | 5 / 59 | |
| 0.3.37 | 5 / 58 | |
| 0.3.36 | 5 / 58 | |
| 0.3.35 | 5 / 58 | |
| 0.3.34 | 5 / 58 | |
| 0.3.33 | 5 / 58 | |
| 0.3.32 | 5 / 58 | |
| 0.3.31 | 5 / 58 | |
| 0.3.30 | 5 / 58 | |
| 0.3.29 | 5 / 58 | |
| 0.3.28 | 5 / 58 | |
| 0.3.27 | 5 / 58 | |
| 0.3.26 | 5 / 58 | |
| 0.3.25 | 5 / 58 | |
| 0.3.24 | 5 / 58 | |
| 0.3.23 | 5 / 58 | |
| 0.3.22 | 5 / 58 | |
| 0.3.21 | 5 / 58 | |
| 0.3.20 | 5 / 58 | |
| 0.3.19 | 5 / 58 | |
| 0.3.18 | 5 / 58 | |
| 0.3.17 | 5 / 58 | |
| 0.3.16 | 5 / 58 | |
| 0.3.15 | 5 / 58 | |
| 0.3.14 | 5 / 61 | |
| 0.3.13 | 5 / 61 | |
| 0.3.12 | 5 / 61 | |
| 0.3.11 | 5 / 61 | |
| 0.3.10 | 5 / 61 | |
| 0.3.9 | 5 / 61 | |
| 0.3.8 | 5 / 61 | |
| 0.3.7 | 5 / 61 |
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.