@descope/sdk-mixins
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 | no-provenance | AI (provenance): Descope org package with long publish history; provenance absence is consistent across all versions. | ai |
Versions (showing 95 of 95)
| Version | Deps | Published |
|---|---|---|
| 0.23.2 | 3 / 45 | |
| 0.23.1 | 3 / 45 | |
| 0.23.0 | 3 / 45 | |
| 0.22.0 | 3 / 45 | |
| 0.21.0 | 3 / 45 | |
| 0.20.0 | 3 / 45 | |
| 0.19.0 | 3 / 45 | |
| 0.18.0 | 3 / 45 | |
| 0.17.1 | 3 / 45 | |
| 0.17.0 | 3 / 45 | |
| 0.16.2 | 3 / 45 | |
| 0.16.1 | 3 / 45 | |
| 0.16.0 | 3 / 45 | |
| 0.15.1 | 3 / 45 | |
| 0.15.0 | 3 / 45 | |
| 0.14.1 | 3 / 45 | |
| 0.14.0 | 3 / 45 | |
| 0.13.16 | 3 / 45 | |
| 0.13.15 | 3 / 45 | |
| 0.13.14 | 3 / 45 | |
| 0.13.13 | 3 / 45 | |
| 0.13.12 | 3 / 45 | |
| 0.13.11 | 3 / 45 | |
| 0.13.10 | 3 / 45 | |
| 0.13.9 | 3 / 45 | |
| 0.13.8 | 3 / 45 | |
| 0.13.7 | 3 / 45 | |
| 0.13.6 | 3 / 45 | |
| 0.13.5 | 3 / 45 | |
| 0.13.4 | 3 / 45 | |
| 0.13.3 | 3 / 45 | |
| 0.13.2 | 3 / 45 | |
| 0.13.1 | 3 / 45 | |
| 0.13.0 | 3 / 45 | |
| 0.12.0 | 3 / 45 | |
| 0.11.3 | 3 / 45 | |
| 0.11.2 | 3 / 45 | |
| 0.11.1 | 3 / 45 | |
| 0.11.0 | 3 / 45 | |
| 0.10.0 | 3 / 45 | |
| 0.9.0 | 3 / 45 | |
| 0.8.0 | 3 / 45 | |
| 0.7.0 | 3 / 45 | |
| 0.6.8 | 3 / 45 | |
| 0.6.7 | 3 / 45 | |
| 0.6.6 | 3 / 45 | |
| 0.6.5 | 3 / 45 | |
| 0.6.4 | 3 / 45 | |
| 0.6.3 | 3 / 45 | |
| 0.6.2 | 3 / 45 | |
| 0.6.1 | 3 / 45 | |
| 0.6.0 | 3 / 45 | |
| 0.5.2 | 3 / 45 | |
| 0.5.1 | 3 / 45 | |
| 0.5.0 | 3 / 44 | |
| 0.4.0 | 3 / 44 | |
| 0.3.2 | 3 / 44 | |
| 0.3.1 | 3 / 44 | |
| 0.3.0 | 3 / 44 | |
| 0.2.44 | 3 / 44 | |
| 0.2.43 | 3 / 44 | |
| 0.2.42 | 3 / 44 | |
| 0.2.41 | 3 / 44 | |
| 0.2.40 | 3 / 44 | |
| 0.2.39 | 3 / 44 | |
| 0.2.38 | 3 / 44 | |
| 0.2.37 | 3 / 44 | |
| 0.2.36 | 3 / 44 | |
| 0.2.35 | 3 / 44 | |
| 0.2.34 | 3 / 44 | |
| 0.2.33 | 3 / 44 | |
| 0.2.32 | 3 / 44 | |
| 0.2.31 | 3 / 44 | |
| 0.2.30 | 3 / 44 | |
| 0.2.29 | 3 / 44 | |
| 0.2.28 | 3 / 44 | |
| 0.2.27 | 3 / 44 | |
| 0.2.26 | 3 / 44 | |
| 0.2.25 | 3 / 44 | |
| 0.2.24 | 3 / 44 | |
| 0.2.23 | 3 / 44 | |
| 0.2.22 | 3 / 44 | |
| 0.2.21 | 3 / 44 | |
| 0.2.20 | 3 / 44 | |
| 0.2.19 | 3 / 44 | |
| 0.2.18 | 3 / 44 | |
| 0.2.17 | 3 / 44 | |
| 0.2.16 | 3 / 44 | |
| 0.2.15 | 3 / 44 | |
| 0.2.14 | 3 / 44 | |
| 0.2.13 | 3 / 44 | |
| 0.2.12 | 3 / 44 | |
| 0.2.11 | 3 / 44 | |
| 0.2.10 | 3 / 44 | |
| 0.2.9 | 3 / 44 |
v0.23.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.
v0.5.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.
v0.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.
v0.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.
v0.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.
v0.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.
v0.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.
v0.2.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.