@vuu-ui/vuu-datatable Apache-2.0 20 versions

@vuu-ui/vuu-datatable

npm

20

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
npm-metadata	no-description	AI (npm-metadata): Stable metadata gap across this org's packages; not a malware signal.	ai	2026/05/29
bogus-package	bogus-package	AI (bogus-package): Monorepo sub-package; missing description/repo/keywords is standard for this package family across 332 versions.	ai	2026/05/25
phantom-deps	phantom-dep:@vuu-ui/vuu-popups	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/20
phantom-deps	phantom-dep:@vuu-ui/vuu-table-extras	AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo packages.	ai	2026/05/20

Versions (showing 20 of 20)

Version	Deps	Published
2.1.8	13 / 0	2026-06-04
2.1.7	13 / 0	2026-05-27
2.1.6	13 / 0	2026-05-27
2.1.5	13 / 0	2026-05-21
2.1.4	13 / 0	2026-05-19
2.1.3	13 / 0	2026-05-19
2.1.2	13 / 0	2026-05-18
2.1.1	13 / 0	2026-05-18
2.1.0	13 / 0	2026-05-14
2.0.0	13 / 0	2026-04-23
1.0.3	13 / 0	2026-04-07
1.0.2	13 / 0	2026-04-07
1.0.1	13 / 0	2026-03-25
1.0.0	13 / 0	2026-03-24
0.13.118	13 / 0	2026-03-23
0.13.117	13 / 0	2026-03-23
0.13.116	13 / 0	2026-03-19
0.13.115	13 / 0	2026-03-19
0.13.104	13 / 0	2026-02-09
0.13.68	13 / 0	2025-10-30

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

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

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.

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

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

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

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