@descope/react-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@descope/audit-management-widget | AI (dependencies): First-party @descope org widget; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@descope/role-management-widget | AI (dependencies): First-party @descope org widget; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@descope/user-management-widget | AI (dependencies): First-party @descope org widget; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@descope/outbound-applications-widget | AI (dependencies): First-party @descope org widget; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@descope/applications-portal-widget | AI (dependencies): First-party @descope org widget; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@descope/access-key-management-widget | AI (dependencies): First-party @descope org widget; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Large established package; lack of provenance is consistent across all prior versions and is not a meaningful risk signal here. | ai |
Versions (showing 100 of 247)
| Version | Deps | Published |
|---|---|---|
| 2.16.2 | 11 / 66 | |
| 2.16.1 | 11 / 66 | |
| 2.16.0 | 11 / 66 | |
| 2.15.0 | 10 / 66 | |
| 2.14.26 | 10 / 66 | |
| 2.14.25 | 10 / 66 | |
| 2.14.24 | 10 / 66 | |
| 2.14.23 | 10 / 66 | |
| 2.14.22 | 10 / 66 | |
| 2.14.21 | 10 / 66 | |
| 2.14.20 | 10 / 66 | |
| 2.14.19 | 10 / 66 | |
| 2.14.18 | 10 / 66 | |
| 2.14.17 | 10 / 66 | |
| 2.14.16 | 10 / 66 | |
| 2.14.15 | 10 / 66 | |
| 2.14.14 | 10 / 66 | |
| 2.14.13 | 10 / 66 | |
| 2.14.12 | 10 / 66 | |
| 2.14.11 | 10 / 66 | |
| 2.14.10 | 10 / 66 | |
| 2.14.9 | 10 / 66 | |
| 2.14.8 | 10 / 66 | |
| 2.14.7 | 10 / 66 | |
| 2.14.6 | 10 / 66 | |
| 2.14.5 | 10 / 66 | |
| 2.14.4 | 10 / 66 | |
| 2.14.3 | 10 / 66 | |
| 2.14.2 | 10 / 66 | |
| 2.14.1 | 10 / 66 | |
| 2.14.0 | 10 / 66 | |
| 2.13.2 | 10 / 66 | |
| 2.13.1 | 10 / 66 | |
| 2.13.0 | 10 / 66 | |
| 2.12.6 | 10 / 66 | |
| 2.12.5 | 10 / 66 | |
| 2.12.4 | 10 / 66 | |
| 2.12.3 | 10 / 66 | |
| 2.12.2 | 10 / 66 | |
| 2.12.1 | 10 / 66 | |
| 2.12.0 | 10 / 65 | |
| 2.11.6 | 10 / 65 | |
| 2.11.5 | 10 / 65 | |
| 2.11.4 | 10 / 65 | |
| 2.11.3 | 10 / 65 | |
| 2.11.2 | 10 / 65 | |
| 2.11.1 | 10 / 65 | |
| 2.11.0 | 10 / 65 | |
| 2.10.0 | 10 / 65 | |
| 2.9.0 | 10 / 65 | |
| 2.8.1 | 10 / 65 | |
| 2.8.0 | 10 / 65 | |
| 2.7.2 | 10 / 65 | |
| 2.7.1 | 10 / 65 | |
| 2.7.0 | 10 / 65 | |
| 2.6.1 | 10 / 65 | |
| 2.6.0 | 10 / 65 | |
| 2.5.0 | 10 / 65 | |
| 2.4.0 | 10 / 65 | |
| 2.3.25 | 10 / 65 | |
| 2.3.24 | 10 / 65 | |
| 2.3.23 | 10 / 65 | |
| 2.3.22 | 10 / 65 | |
| 2.3.21 | 10 / 65 | |
| 2.3.20 | 10 / 65 | |
| 2.3.19 | 10 / 65 | |
| 2.3.18 | 10 / 65 | |
| 2.3.17 | 10 / 65 | |
| 2.3.16 | 10 / 65 | |
| 2.3.15 | 10 / 65 | |
| 2.3.14 | 10 / 65 | |
| 2.3.13 | 10 / 65 | |
| 2.3.12 | 10 / 65 | |
| 2.3.11 | 10 / 65 | |
| 2.3.10 | 10 / 65 | |
| 2.3.9 | 10 / 65 | |
| 2.3.8 | 10 / 65 | |
| 2.3.7 | 10 / 65 | |
| 2.3.6 | 9 / 65 | |
| 2.3.5 | 9 / 65 | |
| 2.3.4 | 9 / 64 | |
| 2.3.3 | 9 / 64 | |
| 2.3.2 | 9 / 64 | |
| 2.3.1 | 9 / 64 | |
| 2.3.0 | 9 / 64 | |
| 2.2.0 | 9 / 64 | |
| 2.1.6 | 9 / 64 | |
| 2.1.5 | 9 / 64 | |
| 2.1.4 | 9 / 64 | |
| 2.1.3 | 9 / 64 | |
| 2.1.2 | 9 / 64 | |
| 2.1.1 | 9 / 64 | |
| 2.1.0 | 9 / 64 | |
| 2.0.78 | 8 / 64 | |
| 2.0.77 | 8 / 64 | |
| 2.0.76 | 8 / 64 | |
| 2.0.75 | 8 / 64 | |
| 2.0.74 | 8 / 64 | |
| 2.0.73 | 8 / 64 | |
| 2.0.72 | 8 / 64 |
v2.14.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.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.
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.