@dxos/react-ui
Low-level React components for DXOS, applying a theme to a core group of primitives
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/types/src/components/Lists/List.d.ts | AI (source-diff): Long-line .d.ts type union, not obfuscated code; readable TS declarations. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-popper | AI (phantom-deps): Radix peer dep used indirectly via other radix components; stable FP. | ai | |
| source-diff | obfuscated-file:dist/types/src/components/Lists/Treegrid.d.ts | AI (source-diff): Same false-positive pattern: minified-looking .d.ts type declarations. | ai | |
| phantom-deps | phantom-dep:@dxos/react-list | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for monorepo peer/re-export patterns. | ai | |
| dependencies | unvetted-dep:@dxos/i18n | AI (dependencies): Same-org monorepo dep pinned to matching version; consistent with coordinated DXOS releases. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-popper | AI (dependencies): Well-known Radix UI primitive; stable ecosystem package, not a risk for this package. | ai | |
| phantom-deps | phantom-dep:@effect-atom/atom-react | AI (phantom-deps): Referenced in config files per finding; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-scroll-area | AI (phantom-deps): Referenced in config files; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/pragmatic-drag-and-drop-hitbox | AI (phantom-deps): Referenced in config files; phantom-dep false positive for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with org-level CI migration; SLSA attestation and monorepo context confirm legitimate transition. | ai | |
| provenance | publisher-changed | AI (provenance): dxos-bot → GitHub Actions is a CI/CD migration; SLSA provenance attestation confirms integrity. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-collapsible | AI (phantom-deps): Same pattern — declared for consumer use, referenced in config files. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-switch | AI (phantom-deps): Same pattern — declared for consumer use, referenced in config files. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-avatar | AI (phantom-deps): Declared as dep for consumers; referenced in config/re-exports, not a direct import. Stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 56 / 14 | |
| 0.9.0 | 55 / 14 | |
| 0.8.3 | 47 / 12 | |
| 0.8.2 | 47 / 12 | |
| 0.8.1 | 46 / 12 | |
| 0.8.0 | 44 / 12 | |
| 0.7.4 | 43 / 12 | |
| 0.7.3 | 43 / 12 | |
| 0.7.2 | 43 / 12 | |
| 0.7.1 | 43 / 12 | |
| 0.7.0 | 43 / 12 | |
| 0.6.13 | 34 / 12 | |
| 0.6.12 | 34 / 12 | |
| 0.6.11 | 34 / 12 | |
| 0.6.10 | 34 / 12 | |
| 0.6.9 | 33 / 12 | |
| 0.6.8 | 33 / 12 | |
| 0.6.7 | 32 / 12 | |
| 0.6.6 | 32 / 12 | |
| 0.6.5 | 32 / 12 | |
| 0.6.4 | 31 / 12 | |
| 0.6.3 | 31 / 12 | |
| 0.6.2 | 31 / 12 | |
| 0.6.1 | 31 / 12 | |
| 0.6.0 | 31 / 12 | |
| 0.5.8 | 31 / 12 | |
| 0.5.7 | 31 / 12 | |
| 0.5.6 | 31 / 12 | |
| 0.5.5 | 31 / 12 | |
| 0.5.4 | 31 / 12 | |
| 0.5.3 | 31 / 13 | |
| 0.5.2 | 31 / 13 |
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
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.
v0.6.6
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.
v0.6.5
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.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.