@vuu-ui/vuu-data-react Apache-2.0 30 versions

@vuu-ui/vuu-data-react

npm

30

Versions

Apache-2.0

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

heswell

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Large monorepo with consistent publish history; missing gitHead is a CI config change, not a malware indicator.	ai	2026/05/30
provenance	no-provenance	AI (provenance): Established package with 333 versions; lack of Sigstore attestation is a process gap, not a security risk here.	ai	2026/05/30
npm-metadata	no-description	AI (npm-metadata): Monorepo sub-package pattern; no description is consistent across the @vuu-ui namespace.	ai	2026/05/30
dependencies	unvetted-dep:@vuu-ui/vuu-filters	AI (dependencies): Sibling monorepo package at matching version; expected coordinated release pattern.	ai	2026/05/20
dependencies	unvetted-dep:@salt-ds/styles	AI (dependencies): Salt DS UI library dependency; stable legitimate dep for this package.	ai	2026/05/20
bogus-package	bogus-package	AI (bogus-package): Monorepo sub-package; missing metadata is typical for this package family.	ai	2026/05/20
dependencies	unvetted-dep:@salt-ds/window	AI (dependencies): Salt DS UI library dependency; stable legitimate dep for this package.	ai	2026/05/20
dependencies	unvetted-dep:@vuu-ui/vuu-layout	AI (dependencies): Sibling monorepo package at matching version; expected coordinated release pattern.	ai	2026/05/20

Versions (showing 30 of 30)

Version	Deps	Published
2.1.8	12 / 4	2026-06-04
2.1.7	12 / 4	2026-05-27
2.1.6	12 / 4	2026-05-27
2.1.5	12 / 4	2026-05-21
2.1.4	12 / 4	2026-05-19
2.1.3	12 / 4	2026-05-19
2.1.2	12 / 4	2026-05-18
2.1.1	12 / 4	2026-05-18
2.1.0	12 / 4	2026-05-14
1.0.3	12 / 4	2026-04-07
1.0.2	12 / 4	2026-04-07
0.13.90	12 / 5	2025-12-12
0.13.88	12 / 5	2025-12-08
0.13.87	12 / 5	2025-12-08
0.13.82	12 / 5	2025-12-03
0.13.81	12 / 5	2025-12-03
0.13.80	12 / 5	2025-12-02
0.13.79	12 / 5	2025-12-02
0.13.78	12 / 5	2025-11-26
0.13.77	12 / 5	2025-11-25
0.13.76	12 / 5	2025-11-24
0.13.75	12 / 5	2025-11-20
0.13.74	12 / 5	2025-11-17
0.13.73	12 / 5	2025-11-10
0.13.72	12 / 5	2025-11-06
0.13.71	12 / 5	2025-11-06
0.13.70	12 / 5	2025-11-04
0.13.69	12 / 5	2025-11-02
0.13.68	12 / 5	2025-10-30
0.13.67	12 / 5	2025-10-30

v2.1.8

1 finding

INFO No provenance attestation provenance

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

v2.1.7

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.6

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v2.1.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: heswell.

LOW No provenance attestation provenance

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

v1.0.3

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.

v1.0.2

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.13.81

1 finding

LOW No provenance attestation provenance

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

v0.13.80

1 finding

LOW No provenance attestation provenance

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

v0.13.79

1 finding

LOW No provenance attestation provenance

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

v0.13.78

1 finding

LOW No provenance attestation provenance

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

v0.13.77

1 finding

LOW No provenance attestation provenance

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

v0.13.76

1 finding

LOW No provenance attestation provenance

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

v0.13.75

1 finding

LOW No provenance attestation provenance

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

v0.13.74

1 finding

LOW No provenance attestation provenance

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

v0.13.73

1 finding

LOW No provenance attestation provenance

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

v0.13.72

1 finding

LOW No provenance attestation provenance

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

v0.13.71

1 finding

LOW No provenance attestation provenance

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

v0.13.70

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

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

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

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.