← Home

@libretexts/davis-vue-table

npm Repository Homepage

Full-featured, accessible DataTable for Vue 3 built on TanStack Table, styled with the Davis Design System

14
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

libretexts

Keywords

vueuitabledatatabletanstacktailwindaccessibilitya11y

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:clsx AI (phantom-deps): Referenced in config/style files, not directly imported in source; stable false positive for this package. ai
phantom-deps phantom-dep:tailwind-merge AI (phantom-deps): Referenced in config/style files, not directly imported in source; stable false positive for this package. ai
phantom-deps phantom-dep:tailwind-variants AI (phantom-deps): Referenced in config/style files, not directly imported in source; stable false positive for this package. ai
phantom-deps phantom-dep:@libretexts/davis-vue AI (phantom-deps): Same-org dependency; expected usage pattern for this monorepo package. ai

Versions (showing 14 of 14)

Version Deps Published
1.10.1 7 / 15
1.10.0 7 / 15
1.9.3 7 / 15
1.9.2 7 / 15
1.9.1 7 / 15
1.9.0 7 / 15
1.8.1 7 / 15
1.8.0 7 / 15
1.7.0 7 / 15
1.6.4 7 / 15
1.6.3 7 / 15
1.6.2 7 / 15
1.6.1 7 / 15
1.6.0 7 / 15

v1.10.1

1 finding
LOW No provenance attestation provenance

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

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.3

1 finding
LOW No provenance attestation provenance

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

v1.9.2

1 finding
LOW No provenance attestation provenance

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

v1.9.0

1 finding
LOW No provenance attestation provenance

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

v1.8.1

1 finding
LOW No provenance attestation provenance

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

v1.8.0

1 finding
LOW No provenance attestation provenance

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

v1.7.0

1 finding
LOW No provenance attestation provenance

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

v1.6.4

1 finding
LOW No provenance attestation provenance

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

v1.6.3

1 finding
LOW No provenance attestation provenance

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

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