@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 47 of 247)
| Version | Deps | Published |
|---|---|---|
| 3.16.6 | 2 / 43 | |
| 3.16.5 | 2 / 43 | |
| 3.16.4 | 2 / 43 | |
| 3.16.3 | 2 / 43 | |
| 3.16.2 | 2 / 43 | |
| 3.16.1 | 2 / 43 | |
| 3.16.0 | 2 / 43 | |
| 3.15.6 | 2 / 43 | |
| 3.15.5 | 2 / 43 | |
| 3.15.4 | 2 / 43 | |
| 3.15.3 | 2 / 43 | |
| 3.15.2 | 2 / 43 | |
| 3.15.1 | 2 / 43 | |
| 3.15.0 | 2 / 43 | |
| 3.14.1 | 2 / 43 | |
| 3.14.0 | 2 / 43 | |
| 3.13.3 | 2 / 43 | |
| 3.13.2 | 2 / 43 | |
| 3.13.1 | 2 / 43 | |
| 3.13.0 | 2 / 43 | |
| 3.12.10 | 2 / 43 | |
| 3.12.9 | 2 / 43 | |
| 3.12.8 | 2 / 43 | |
| 3.12.7 | 2 / 43 | |
| 3.12.6 | 2 / 43 | |
| 3.12.5 | 2 / 43 | |
| 3.12.4 | 2 / 43 | |
| 3.12.3 | 2 / 43 | |
| 3.12.2 | 2 / 43 | |
| 3.12.1 | 2 / 43 | |
| 3.12.0 | 2 / 43 | |
| 3.11.25 | 2 / 43 | |
| 3.11.24 | 2 / 43 | |
| 3.11.23 | 2 / 43 | |
| 3.11.22 | 2 / 43 | |
| 3.11.21 | 2 / 43 | |
| 3.11.20 | 2 / 43 | |
| 3.11.19 | 2 / 43 | |
| 3.11.18 | 2 / 43 | |
| 3.11.17 | 2 / 43 | |
| 3.11.16 | 2 / 43 | |
| 3.11.15 | 2 / 43 | |
| 3.11.14 | 2 / 43 | |
| 3.11.13 | 2 / 43 | |
| 3.11.12 | 2 / 43 | |
| 3.11.11 | 2 / 43 | |
| 3.11.10 | 2 / 43 |
v3.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.