@workos-inc/widgets
A suite of React components providing functionality for enterprise app workflows.
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/lib/change-password-dialog.js | AI (source-diff): Readable TSC-emitted CJS build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/esm/lib/change-password-dialog.js | AI (source-diff): Readable TSC-emitted ESM build output, not obfuscation. | ai | |
| dependencies | unvetted-dep:@repo/api | AI (dependencies): Monorepo internal workspace package pinned 0.0.0; stable for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-popover | AI (phantom-deps): @radix-ui/react-popover is declared as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 5 / 21 | |
| 1.14.1 | 5 / 21 | |
| 1.14.0 | 5 / 21 | |
| 1.13.0 | 5 / 21 | |
| 1.12.0 | 5 / 21 | |
| 1.11.0 | 5 / 21 | |
| 1.10.2 | 5 / 21 | |
| 1.10.1 | 5 / 21 | |
| 1.10.0 | 5 / 21 | |
| 1.9.1 | 5 / 21 | |
| 1.9.0 | 5 / 21 | |
| 1.8.1 | 8 / 25 | |
| 1.8.0 | 8 / 24 | |
| 1.7.2 | 8 / 21 | |
| 1.7.1 | 8 / 21 | |
| 1.7.0 | 8 / 21 | |
| 1.6.1 | 8 / 21 | |
| 1.6.0 | 8 / 21 | |
| 1.5.1 | 8 / 14 | |
| 1.5.0 | 8 / 13 | |
| 1.4.2 | 8 / 12 | |
| 1.4.1 | 8 / 13 | |
| 1.4.0 | 8 / 12 | |
| 1.3.1 | 8 / 12 | |
| 1.3.0 | 8 / 12 | |
| 1.2.1 | 8 / 12 | |
| 1.2.0 | 8 / 11 | |
| 1.1.3 | 8 / 10 | |
| 1.1.0 | 9 / 9 | |
| 1.0.1 | 4 / 9 | |
| 1.0.0 | 4 / 9 |
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.