@descope/web-components-ui
Descope Web Components UI Library
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/umd/descope-multi-sso.js | AI (source-diff): Standard webpack UMD bundle; minification is expected for this package's dist output. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-month-day-field.js | AI (source-diff): Standard webpack UMD bundle for new first-party Descope component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/6618.js | AI (source-diff): Standard webpack UMD bundle from Descope's own build pipeline; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-month-day-field-picker.js | AI (source-diff): Standard webpack UMD bundle for new first-party Descope component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/9265.js | AI (source-diff): Standard webpack UMD bundle from Descope's own build pipeline; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/8350.js | AI (source-diff): Standard webpack UMD bundle from Descope's own build pipeline; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-text-field.js | AI (source-diff): Standard webpack UMD bundle for new first-party Descope component; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-user-passkeys.js | AI (source-diff): Standard webpack UMD bundle with license header; matches existing build pattern for all other component bundles in this package. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-outbound-app-button | AI (dependencies): Internal @descope-ui scoped sibling; consistent monorepo versioning pattern. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-image | AI (dependencies): Internal @descope-ui scoped sibling; consistent monorepo versioning pattern across all releases. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-ponyhot | AI (dependencies): Internal @descope-ui scoped sibling; consistent monorepo versioning pattern. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-anchored | AI (dependencies): Newly added internal @descope-ui scoped sibling; fits established monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@descope-ui/descope-anchored | AI (phantom-deps): Referenced in config files as expected for monorepo component; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@descope-ui/descope-ponyhot | AI (phantom-deps): Monorepo sibling package; declared in package.json as a runtime dep, config-only reference is expected. | ai | |
| source-diff | obfuscated-file:stories/helpers.js | AI (source-diff): Plain readable JS Storybook helper; long lines are template literals, not obfuscation. | ai | |
| source-diff | obfuscated-file:stories/icons/base64png.js | AI (source-diff): Inline base64 data URI for PNG icon asset; not executable obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-multi-line-mappings.js | AI (source-diff): Standard webpack-minified UMD bundle for new @descope-ui/descope-multi-line-mappings component. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-anchored.js | AI (source-diff): Standard webpack-minified UMD bundle for new @descope-ui/descope-anchored component. | ai | |
| source-diff | obfuscated-file:stories/icons/base64svg.js | AI (source-diff): Inline base64 data URI for SVG icon asset; not executable obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-multi-select-combo-box.js | AI (source-diff): Standard webpack-minified UMD bundle for new @descope-ui/descope-multi-select-combo-box component. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.14.1 | 56 / 44 | |
| 3.13.2 | 55 / 44 | |
| 3.13.1 | 55 / 44 | |
| 3.13.0 | 55 / 44 | |
| 3.12.1 | 52 / 44 | |
| 3.11.7 | 52 / 44 | |
| 3.11.6 | 52 / 44 | |
| 3.11.4 | 52 / 44 | |
| 3.11.1 | 52 / 44 | |
| 3.10.1 | 51 / 44 | |
| 3.10.0 | 51 / 44 | |
| 3.9.2 | 51 / 44 | |
| 3.9.1 | 51 / 44 | |
| 3.9.0 | 51 / 44 | |
| 3.7.3 | 49 / 44 | |
| 3.7.2 | 49 / 44 | |
| 3.7.1 | 49 / 44 | |
| 3.7.0 | 48 / 44 | |
| 3.6.0 | 48 / 44 | |
| 3.5.1 | 48 / 44 | |
| 3.3.4 | 48 / 44 | |
| 3.3.3 | 48 / 44 | |
| 3.3.2 | 48 / 44 | |
| 3.3.1 | 48 / 44 | |
| 3.3.0 | 48 / 44 | |
| 3.2.1 | 48 / 44 | |
| 3.2.0 | 48 / 44 | |
| 3.1.13 | 47 / 44 | |
| 3.1.12 | 47 / 44 | |
| 3.1.11 | 47 / 44 | |
| 3.1.7 | 47 / 44 | |
| 3.1.5 | 47 / 44 | |
| 3.1.3 | 47 / 44 | |
| 3.1.2 | 47 / 44 | |
| 3.1.1 | 47 / 44 | |
| 3.1.0 | 47 / 44 | |
| 3.0.10 | 47 / 44 |
v3.14.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.7
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
8 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
7 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.