← Home

@dxos/lit-grid

npm Repository Homepage

A grid Web Component using Lit

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
source-diff large-new-source-files AI (source-diff): New files are bundled dist output from added drag-and-drop dependency, not injected code. ai
source-diff source-size-tripled AI (source-diff): Size growth explained by legitimate new dependency's bundled dist artifacts. ai
publish-pattern new-deps-added AI (publish-pattern): Adds well-known @atlaskit package; consistent with DXOS grid component functionality. ai
provenance publisher-changed AI (provenance): Transition from dxos-bot to GitHub Actions is a CI pipeline change within the same dxos org, confirmed by SLSA provenance attestation. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer removal aligns with org-level CI automation takeover; no signs of hostile takeover given SLSA attestation and stable repo. ai
bogus-package bogus-package AI (bogus-package): Sparse README/keywords are typical for internal monorepo packages; 244 versions and 2 approved-dep edges confirm legitimacy. ai

Versions (showing 15 of 15)

Version Deps Published
0.10.0 2 / 2
0.9.0 2 / 2
0.8.3 2 / 1
0.8.2 2 / 1
0.8.1 2 / 1
0.8.0 2 / 1
0.7.4 2 / 1
0.7.3 2 / 1
0.7.2 2 / 1
0.7.1 2 / 0
0.7.0 2 / 0
0.6.13 1 / 0
0.6.12 1 / 0
0.6.11 1 / 0
0.6.10 1 / 0

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.