@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, 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@descope-ui/descope-honeypot | AI (phantom-deps): Used via config/registration pattern typical of web-components suites, not a real phantom dep. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-honeypot | AI (dependencies): First-party sibling package in same monorepo, version-locked with rest of suite. | ai | |
| source-diff | obfuscated-file:dist/umd/67.js | AI (source-diff): Webpack-bundled UMD chunk, banner confirms build output not obfuscation. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-filter | AI (dependencies): Same-org monorepo sibling package, consistent with existing dependency pattern. | ai | |
| source-diff | obfuscated-file:dist/umd/descope-filter.js | AI (source-diff): Webpack-bundled UMD chunk, banner confirms build output not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/umd/9439.js | AI (source-diff): Webpack-bundled UMD chunk, banner confirms build output not obfuscation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Cosmetic metadata gap, consistent across Descope monorepo packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Spam heuristics from missing description/repo fields, not actual spam. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-month-day-field | AI (dependencies): First-party @descope-ui monorepo package pinned to same version. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-month-day-field-picker | AI (dependencies): First-party @descope-ui monorepo package pinned to same version. | ai | |
| 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/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/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/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-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/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/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 | |
| 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 | |
| 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-anchored | AI (dependencies): Newly added internal @descope-ui scoped sibling; fits established monorepo pattern. | ai | |
| dependencies | unvetted-dep:@descope-ui/descope-ponyhot | AI (dependencies): Internal @descope-ui scoped sibling; consistent monorepo versioning pattern. | 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: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:stories/icons/base64svg.js | AI (source-diff): Inline base64 data URI for SVG icon asset; not executable obfuscation. | 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: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 | |
| 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-anchored.js | AI (source-diff): Standard webpack-minified UMD bundle for new @descope-ui/descope-anchored component. | ai |
Versions (showing 100 of 135)
| Version | Deps | Published |
|---|---|---|
| 3.18.2 | 57 / 45 | |
| 3.18.1 | 57 / 45 | |
| 3.18.0 | 57 / 45 | |
| 3.17.0 | 56 / 45 | |
| 3.16.4 | 56 / 45 | |
| 3.16.3 | 56 / 45 | |
| 3.16.2 | 56 / 44 | |
| 3.16.1 | 56 / 44 | |
| 3.14.10 | 56 / 44 | |
| 3.14.9 | 56 / 44 | |
| 3.14.8 | 56 / 44 | |
| 3.14.7 | 56 / 44 | |
| 3.14.6 | 56 / 44 | |
| 3.14.5 | 56 / 44 | |
| 3.14.4 | 56 / 44 | |
| 3.14.3 | 56 / 44 | |
| 3.14.2 | 56 / 44 | |
| 3.14.1 | 56 / 44 | |
| 3.14.0 | 56 / 44 | |
| 3.13.2 | 55 / 44 | |
| 3.13.1 | 55 / 44 | |
| 3.13.0 | 55 / 44 | |
| 3.12.1 | 52 / 44 | |
| 3.12.0 | 52 / 44 | |
| 3.11.8 | 52 / 44 | |
| 3.11.7 | 52 / 44 | |
| 3.11.6 | 52 / 44 | |
| 3.11.5 | 52 / 44 | |
| 3.11.4 | 52 / 44 | |
| 3.11.3 | 52 / 44 | |
| 3.11.2 | 52 / 44 | |
| 3.11.1 | 52 / 44 | |
| 3.10.2 | 51 / 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.5.0 | 48 / 44 | |
| 3.4.0 | 48 / 44 | |
| 3.3.5 | 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.2 | 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.10 | 47 / 44 | |
| 3.1.9 | 47 / 44 | |
| 3.1.8 | 47 / 44 | |
| 3.1.7 | 47 / 44 | |
| 3.1.6 | 47 / 44 | |
| 3.1.5 | 47 / 44 | |
| 3.1.4 | 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 | |
| 3.0.9 | 47 / 44 | |
| 3.0.8 | 47 / 44 | |
| 3.0.7 | 47 / 44 | |
| 3.0.6 | 46 / 44 | |
| 3.0.5 | 46 / 44 | |
| 3.0.4 | 46 / 44 | |
| 3.0.3 | 46 / 43 | |
| 3.0.2 | 46 / 43 | |
| 3.0.1 | 46 / 43 | |
| 3.0.0 | 46 / 43 | |
| 2.3.3 | 46 / 43 | |
| 2.3.2 | 46 / 43 | |
| 2.3.1 | 46 / 43 | |
| 2.3.0 | 46 / 43 | |
| 2.2.59 | 46 / 43 | |
| 2.2.58 | 46 / 43 | |
| 2.2.57 | 46 / 43 | |
| 2.2.56 | 46 / 43 | |
| 2.2.55 | 46 / 43 | |
| 2.2.54 | 46 / 43 | |
| 2.2.53 | 46 / 43 | |
| 2.2.52 | 46 / 43 | |
| 2.2.51 | 46 / 43 | |
| 2.2.50 | 46 / 43 | |
| 2.2.49 | 46 / 43 | |
| 2.2.48 | 46 / 43 | |
| 2.2.47 | 46 / 43 | |
| 2.2.46 | 46 / 43 | |
| 2.2.45 | 46 / 43 | |
| 2.2.44 | 46 / 43 |
v3.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator. Artifact: bundled (webpack) — bundler banner in the scanned head, but the file is larger than the scan window and its remainder is unclassified, so this is not a clean bill of health.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.