@libretexts/davis-vue
An a11y-first UI library for Vue
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Utility library used in component implementations; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Utility library used in component implementations; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tailwind-variants | AI (phantom-deps): Utility library used in component implementations; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Transitive dependency of @headlessui/vue; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@libretexts/davis-core | AI (phantom-deps): Same-org scoped dependency; stable pattern for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.10.1 | 6 / 15 | |
| 1.10.0 | 6 / 15 | |
| 1.9.3 | 6 / 15 | |
| 1.9.2 | 6 / 15 | |
| 1.9.1 | 6 / 15 | |
| 1.9.0 | 6 / 15 | |
| 1.8.1 | 6 / 15 | |
| 1.8.0 | 6 / 15 | |
| 1.7.0 | 6 / 15 | |
| 1.6.4 | 6 / 15 | |
| 1.6.3 | 5 / 15 | |
| 1.6.2 | 5 / 15 | |
| 1.6.1 | 5 / 15 | |
| 1.6.0 | 5 / 15 | |
| 1.5.0 | 5 / 15 | |
| 1.4.0 | 5 / 15 | |
| 1.3.2 | 2 / 3 | |
| 1.3.1 | 2 / 3 | |
| 1.3.0 | 2 / 3 | |
| 1.2.1 | 2 / 3 | |
| 1.2.0 | 2 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.