@3mo/data-grid No license 28 versions

@3mo/data-grid

npm Repository Homepage

28

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

manuelmolickiarshia11djulian.molickiavorobiov_artelogic

Keywords

litweb-componentmaterialdata-grid

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@3mo/menu	AI (phantom-deps): Same-org monorepo component; phantom-dep heuristic unreliable for peer/transitive usage patterns in web component libraries.	ai	2026/05/04
phantom-deps	phantom-dep:@3mo/select-field	AI (phantom-deps): Same-org monorepo component; phantom-dep heuristic unreliable for this package's usage patterns.	ai	2026/05/04

Versions (showing 28 of 128)

Version	Deps	Published
0.8.16	29 / 0	2024-06-11
0.8.15	29 / 0	2024-06-10
0.8.14	29 / 0	2024-06-10
0.8.13	29 / 0	2024-06-10
0.8.12	29 / 0	2024-06-09
0.8.11	29 / 0	2024-06-09
0.8.10	29 / 0	2024-06-08
0.8.9	29 / 0	2024-06-08
0.8.8	30 / 0	2024-06-07
0.8.7	30 / 0	2024-06-07
0.8.6	29 / 0	2024-06-07
0.8.5	29 / 0	2024-06-07
0.8.4	29 / 0	2024-05-16
0.8.3	29 / 0	2024-05-16
0.8.2	29 / 0	2024-05-16
0.8.1	29 / 0	2024-05-15
0.8.0	29 / 0	2024-05-15
0.7.3	29 / 0	2024-05-15
0.7.2	29 / 0	2024-05-15
0.7.1	29 / 0	2024-05-14
0.7.0	29 / 0	2024-05-13
0.6.6	29 / 0	2024-05-07
0.6.5	29 / 0	2024-05-07
0.6.4	29 / 0	2024-05-07
0.6.3	29 / 0	2024-05-06
0.6.2	29 / 0	2024-05-06
0.6.1	29 / 0	2024-05-05
0.6.0	29 / 0	2024-05-05

v0.8.16

1 finding

LOW No provenance attestation provenance

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

v0.8.15

1 finding

LOW No provenance attestation provenance

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

v0.8.14

1 finding

LOW No provenance attestation provenance

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

v0.8.13

1 finding

LOW No provenance attestation provenance

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

v0.8.12

1 finding

LOW No provenance attestation provenance

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

v0.8.11

1 finding

LOW No provenance attestation provenance

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

v0.8.10

1 finding

LOW No provenance attestation provenance

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

v0.8.9

1 finding

LOW No provenance attestation provenance

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

v0.8.8

1 finding

LOW No provenance attestation provenance

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

v0.8.7

1 finding

LOW No provenance attestation provenance

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

v0.8.6

1 finding

LOW No provenance attestation provenance

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

v0.8.5

1 finding

LOW No provenance attestation provenance

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

v0.8.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: avorobiov_artelogic → arshia11d (on 2024-05-16, known maintainer) provenance

This version was published by a different npm account (arshia11d) than the most recent previously approved version (avorobiov_artelogic) on 2024-05-16, but arshia11d is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: arshia11d → avorobiov_artelogic (on 2024-05-16, known maintainer) provenance

This version was published by a different npm account (avorobiov_artelogic) than the most recent previously approved version (arshia11d) on 2024-05-16, but avorobiov_artelogic is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.2

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.6.5

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.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.