@descope/web-component
Descope WC
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/mixins/componentConditionsMixin.js | AI (source-diff): Standard Rollup/Terser minified output; stable pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/esm/mixins/componentConditionsMixin.js | AI (source-diff): ESM counterpart of same minified mixin; stable pattern. | ai | |
| source-diff | obfuscated-file:dist/cjs/helpers/realtime-conditions/evaluator.js | AI (source-diff): Minified condition evaluator helper; no suspicious content. | ai | |
| source-diff | obfuscated-file:dist/esm/helpers/realtime-conditions/evaluator.js | AI (source-diff): ESM counterpart of same minified evaluator; stable pattern. | ai | |
| phantom-deps | phantom-dep:@fingerprintjs/fingerprintjs-pro | AI (phantom-deps): Listed as a runtime dependency in package.json; phantom-dep heuristic misfires here as it may be loaded dynamically. | ai |
Versions (showing 100 of 247)
| Version | Deps | Published |
|---|---|---|
| 3.43.8 | 6 / 46 | |
| 3.43.7 | 6 / 46 | |
| 3.43.6 | 6 / 46 | |
| 3.43.5 | 6 / 46 | |
| 3.43.4 | 6 / 46 | |
| 3.43.3 | 6 / 46 | |
| 3.43.2 | 6 / 46 | |
| 3.43.1 | 6 / 46 | |
| 3.43.0 | 6 / 46 | |
| 3.42.3 | 6 / 46 | |
| 3.42.2 | 6 / 46 | |
| 3.42.1 | 6 / 46 | |
| 3.42.0 | 6 / 46 | |
| 3.41.1 | 6 / 46 | |
| 3.41.0 | 6 / 46 | |
| 3.40.9 | 6 / 46 | |
| 3.40.8 | 6 / 46 | |
| 3.40.7 | 6 / 46 | |
| 3.40.6 | 6 / 46 | |
| 3.40.5 | 6 / 46 | |
| 3.40.4 | 6 / 46 | |
| 3.40.3 | 6 / 46 | |
| 3.40.2 | 6 / 46 | |
| 3.40.1 | 6 / 46 | |
| 3.40.0 | 6 / 46 | |
| 3.39.3 | 6 / 46 | |
| 3.39.2 | 6 / 46 | |
| 3.39.1 | 6 / 46 | |
| 3.39.0 | 6 / 46 | |
| 3.38.2 | 6 / 46 | |
| 3.38.1 | 6 / 46 | |
| 3.38.0 | 6 / 46 | |
| 3.37.0 | 6 / 43 | |
| 3.36.1 | 6 / 43 | |
| 3.36.0 | 6 / 43 | |
| 3.35.1 | 6 / 43 | |
| 3.35.0 | 6 / 43 | |
| 3.34.1 | 6 / 43 | |
| 3.34.0 | 6 / 43 | |
| 3.33.0 | 6 / 43 | |
| 3.32.11 | 6 / 43 | |
| 3.32.10 | 6 / 43 | |
| 3.32.9 | 6 / 43 | |
| 3.32.8 | 6 / 43 | |
| 3.32.7 | 6 / 43 | |
| 3.32.6 | 6 / 43 | |
| 3.32.5 | 6 / 43 | |
| 3.32.4 | 6 / 43 | |
| 3.32.3 | 6 / 43 | |
| 3.32.2 | 6 / 43 | |
| 3.32.1 | 6 / 43 | |
| 3.32.0 | 6 / 43 | |
| 3.31.3 | 6 / 43 | |
| 3.31.2 | 6 / 43 | |
| 3.31.1 | 6 / 43 | |
| 3.27.2 | 5 / 43 | |
| 3.27.1 | 5 / 43 | |
| 3.27.0 | 5 / 43 | |
| 3.26.0 | 5 / 43 | |
| 3.25.3 | 5 / 43 | |
| 3.25.2 | 5 / 43 | |
| 3.25.1 | 5 / 43 | |
| 3.25.0 | 5 / 43 | |
| 3.24.2 | 5 / 43 | |
| 3.24.1 | 5 / 43 | |
| 3.24.0 | 5 / 43 | |
| 3.23.2 | 5 / 43 | |
| 3.23.1 | 5 / 43 | |
| 3.23.0 | 5 / 43 | |
| 3.22.2 | 3 / 43 | |
| 3.22.1 | 3 / 43 | |
| 3.22.0 | 3 / 43 | |
| 3.21.1 | 2 / 43 | |
| 3.21.0 | 2 / 43 | |
| 3.20.3 | 2 / 43 | |
| 3.20.2 | 2 / 43 | |
| 3.20.1 | 2 / 43 | |
| 3.20.0 | 2 / 43 | |
| 3.19.10 | 2 / 43 | |
| 3.19.9 | 2 / 43 | |
| 3.19.8 | 2 / 43 | |
| 3.19.7 | 2 / 43 | |
| 3.19.6 | 2 / 43 | |
| 3.19.5 | 2 / 43 | |
| 3.19.4 | 2 / 43 | |
| 3.19.3 | 2 / 43 | |
| 3.19.2 | 2 / 43 | |
| 3.19.1 | 2 / 43 | |
| 3.19.0 | 2 / 43 | |
| 3.18.3 | 2 / 43 | |
| 3.18.2 | 2 / 43 | |
| 3.18.1 | 2 / 43 | |
| 3.18.0 | 2 / 43 | |
| 3.17.6 | 2 / 43 | |
| 3.17.5 | 2 / 43 | |
| 3.17.4 | 2 / 43 | |
| 3.17.3 | 2 / 43 | |
| 3.17.2 | 2 / 43 | |
| 3.17.1 | 2 / 43 | |
| 3.17.0 | 2 / 43 |
v3.43.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.42.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.