@vuu-ui/vuu-layout Apache-2.0 51 versions

@vuu-ui/vuu-layout

npm

VUU Layout Components

51

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): Trusted publisher with long track record; likely a publish environment change, not a supply chain risk.	ai	2026/05/28
dependencies	unvetted-dep:@vuu-ui/vuu-filters	AI (dependencies): Same-org monorepo sibling; versioned in lockstep with this package.	ai	2026/05/24
dependencies	unvetted-dep:@vuu-ui/vuu-datatable	AI (dependencies): Same-org monorepo sibling; versioned in lockstep with this package.	ai	2026/05/24
dependencies	unvetted-dep:@vuu-ui/vuu-data-react	AI (dependencies): Same-org monorepo sibling; versioned in lockstep with this package.	ai	2026/05/24
bogus-package	bogus-package	AI (bogus-package): Monorepo sub-package; sparse metadata is expected, not indicative of spam.	ai	2026/05/18
phantom-deps	phantom-dep:@vuu-ui/vuu-datatable	AI (phantom-deps): Same-org sibling dep; heuristic false positive for monorepo packages.	ai	2026/05/18
phantom-deps	phantom-dep:@vuu-ui/vuu-table	AI (phantom-deps): Same-org sibling dep; heuristic false positive for monorepo packages.	ai	2026/05/18
phantom-deps	phantom-dep:@vuu-ui/vuu-popups	AI (phantom-deps): Same-org sibling dep; heuristic false positive for monorepo packages.	ai	2026/05/18
phantom-deps	phantom-dep:@vuu-ui/vuu-filters	AI (phantom-deps): Same-org sibling dep; heuristic false positive for monorepo packages.	ai	2026/05/18

Versions (showing 51 of 65)

View all versions

Version	Deps	Published
2.1.8	10 / 2	2026-06-04
2.1.7	10 / 2	2026-05-27
2.1.6	10 / 2	2026-05-27
2.1.5	10 / 2	2026-05-21
2.1.4	10 / 2	2026-05-19
2.1.3	10 / 2	2026-05-19
2.1.2	10 / 2	2026-05-18
2.1.1	10 / 2	2026-05-18
2.1.0	10 / 2	2026-05-14
2.0.0	10 / 2	2026-04-23
1.0.3	10 / 2	2026-04-07
1.0.2	10 / 2	2026-04-07
1.0.1	10 / 2	2026-03-25
1.0.0	10 / 2	2026-03-24
0.13.118	10 / 2	2026-03-23
0.13.117	10 / 2	2026-03-23
0.13.116	10 / 2	2026-03-19
0.13.115	10 / 2	2026-03-19
0.13.114	10 / 2	2026-03-11
0.13.113	10 / 2	2026-03-06
0.13.112	10 / 2	2026-03-03
0.13.111	10 / 2	2026-03-02
0.13.110	10 / 2	2026-02-25
0.13.109	10 / 2	2026-02-13
0.13.108	10 / 2	2026-02-12
0.13.107	10 / 2	2026-02-11
0.13.106	10 / 2	2026-02-10
0.13.105	10 / 2	2026-02-09
0.13.104	10 / 2	2026-02-09
0.13.103	10 / 2	2026-02-09
0.13.102	10 / 2	2026-02-09
0.13.101	10 / 2	2026-02-06
0.13.100	10 / 2	2026-02-05
0.13.99	10 / 2	2026-02-05
0.13.98	10 / 2	2026-02-04
0.13.97	10 / 2	2026-02-02
0.13.96	10 / 2	2026-02-02
0.13.95	10 / 2	2026-02-02
0.13.93	10 / 2	2025-12-16
0.13.92	10 / 2	2025-12-15
0.13.91	10 / 2	2025-12-15
0.13.90	10 / 2	2025-12-12
0.13.89	10 / 2	2025-12-10
0.13.88	10 / 2	2025-12-08
0.13.87	10 / 2	2025-12-08
0.13.86	10 / 2	2025-12-08
0.13.85	10 / 2	2025-12-08
0.13.84	10 / 2	2025-12-05
0.13.83	10 / 2	2025-12-03
0.13.82	10 / 2	2025-12-03
0.13.81	10 / 2	2025-12-03

v2.1.8

1 finding

LOW No provenance attestation provenance

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

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.6

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.1.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.

v2.0.0

1 finding

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

v1.0.1

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

v0.13.118

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

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.

v0.13.116

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.

v0.13.115

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.

v0.13.114

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.

v0.13.113

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.

v0.13.112

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

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

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.

v0.13.109

1 finding

LOW No provenance attestation provenance

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

v0.13.108

1 finding

LOW No provenance attestation provenance

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

v0.13.107

1 finding

LOW No provenance attestation provenance

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

v0.13.106

1 finding

LOW No provenance attestation provenance

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

v0.13.105

1 finding

LOW No provenance attestation provenance

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

v0.13.104

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

1 finding

LOW No provenance attestation provenance

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

v0.13.102

1 finding

LOW No provenance attestation provenance

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

v0.13.101

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

1 finding

LOW No provenance attestation provenance

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

v0.13.99

1 finding

LOW No provenance attestation provenance

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

v0.13.98

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

1 finding

LOW No provenance attestation provenance

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

v0.13.96

1 finding

LOW No provenance attestation provenance

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

v0.13.95

1 finding

LOW No provenance attestation provenance

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

v0.13.93

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

1 finding

LOW No provenance attestation provenance

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

v0.13.91

1 finding

LOW No provenance attestation provenance

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

v0.13.90

1 finding

LOW No provenance attestation provenance

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

v0.13.89

1 finding

LOW No provenance attestation provenance

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

v0.13.88

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.13.85

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

1 finding

LOW No provenance attestation provenance

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

v0.13.83

1 finding

LOW No provenance attestation provenance

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

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.