← Home

@dxos/react-ui-grid

npm Repository Homepage

React component which manages a `dx-grid` Lit web component.

15
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): dxos migrated publishing from dxos-bot to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD pipeline. ai
maintainer-change maintainer-removed AI (maintainer-change): Org-level CI transition; consistent with dxos-bot → GitHub Actions migration across the monorepo. 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:@dxos/util AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive for this package. ai
phantom-deps phantom-dep:@radix-ui/react-popper AI (phantom-deps): Referenced in config files per finding; not a real phantom dep concern for this package. ai

Versions (showing 15 of 15)

Version Deps Published
0.10.0 11 / 11
0.9.0 11 / 11
0.8.3 11 / 10
0.8.2 11 / 10
0.8.1 10 / 10
0.8.0 10 / 10
0.7.4 10 / 10
0.7.3 10 / 10
0.7.2 10 / 10
0.7.1 10 / 10
0.7.0 10 / 10
0.6.13 5 / 6
0.6.12 5 / 6
0.6.11 5 / 6
0.6.10 5 / 6

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.10

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.