@dxos/react-ui-list
A list component.
6
Versions
MIT
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
richburdonmarik_dwittjosiahdxos-botmykola-vrmchk
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dxos/echo | AI (dependencies): Internal DXOS monorepo sibling package; consistently co-versioned across all releases. | ai | |
| provenance | publisher-changed | AI (provenance): DXOS migrated CI from dxos-bot to GitHub Actions; SLSA attestation confirms legitimate CI publish. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with CI pipeline migration for DXOS monorepo; not indicative of takeover. | ai | |
| phantom-deps | phantom-dep:@dxos/react-ui-attention | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo component; sparse README and no keywords are expected for org-internal packages. | ai | |
| phantom-deps | phantom-dep:@preact/signals-core | AI (phantom-deps): Referenced in config files; transitive signals dependency, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@dxos/react-ui-types | AI (phantom-deps): Same-org monorepo dep; declared but not directly imported is a common monorepo pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 19 / 11 | |
| 0.9.0 | 18 / 8 | |
| 0.8.3 | 14 / 11 | |
| 0.8.2 | 15 / 11 | |
| 0.8.1 | 14 / 11 | |
| 0.8.0 | 13 / 11 |
v0.10.0
1 finding
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.