@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 47 of 247)
| Version | Deps | Published |
|---|---|---|
| 2.0.71 | 8 / 64 | |
| 2.0.70 | 8 / 64 | |
| 2.0.69 | 8 / 64 | |
| 2.0.68 | 8 / 64 | |
| 2.0.67 | 8 / 64 | |
| 2.0.66 | 8 / 64 | |
| 2.0.65 | 8 / 64 | |
| 2.0.64 | 8 / 64 | |
| 2.0.63 | 8 / 64 | |
| 2.0.62 | 8 / 64 | |
| 2.0.61 | 8 / 64 | |
| 2.0.60 | 8 / 64 | |
| 2.0.59 | 8 / 64 | |
| 2.0.58 | 8 / 63 | |
| 2.0.57 | 8 / 63 | |
| 2.0.56 | 8 / 63 | |
| 2.0.55 | 8 / 63 | |
| 2.0.54 | 8 / 63 | |
| 2.0.53 | 8 / 63 | |
| 2.0.52 | 8 / 63 | |
| 2.0.51 | 8 / 63 | |
| 2.0.50 | 8 / 63 | |
| 2.0.49 | 8 / 63 | |
| 2.0.48 | 8 / 63 | |
| 2.0.47 | 8 / 63 | |
| 2.0.46 | 8 / 63 | |
| 2.0.45 | 8 / 63 | |
| 2.0.44 | 8 / 63 | |
| 2.0.43 | 7 / 58 | |
| 2.0.42 | 7 / 58 | |
| 2.0.41 | 7 / 58 | |
| 2.0.40 | 7 / 58 | |
| 2.0.39 | 7 / 58 | |
| 2.0.38 | 7 / 58 | |
| 2.0.37 | 7 / 58 | |
| 2.0.36 | 7 / 58 | |
| 2.0.35 | 7 / 58 | |
| 2.0.34 | 7 / 58 | |
| 2.0.33 | 7 / 58 | |
| 2.0.32 | 7 / 58 | |
| 2.0.31 | 7 / 58 | |
| 2.0.30 | 7 / 58 | |
| 2.0.29 | 7 / 58 | |
| 2.0.28 | 7 / 58 | |
| 2.0.27 | 7 / 58 | |
| 2.0.26 | 7 / 58 | |
| 2.0.25 | 7 / 58 |
v2.0.71
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.70
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.69
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.68
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.67
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.66
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.65
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.64
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.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
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.47
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.46
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.45
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.44
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.43
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.42
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.41
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.40
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.39
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.38
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.37
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.36
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.35
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.34
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.33
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.32
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.31
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.30
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.29
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.28
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.27
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.26
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.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.