@libretexts/davis-react
An a11y-first UI library for React
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/components/drawer.cjs | AI (source-diff): Standard Rollup/Vite CJS bundle output; long lines are minified but readable React component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/components/listbox.cjs | AI (source-diff): Standard Rollup/Vite minified CJS bundle output; readable component logic, no obfuscation or malicious payload. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Bundled at build time; not directly imported in source but legitimately used as a runtime dep. | ai | |
| phantom-deps | phantom-dep:tailwind-variants | AI (phantom-deps): Bundled at build time; not directly imported in source but legitimately used as a runtime dep. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.10.1 | 4 / 19 | |
| 1.10.0 | 4 / 19 | |
| 1.9.3 | 4 / 19 | |
| 1.9.2 | 4 / 19 | |
| 1.9.1 | 4 / 19 | |
| 1.9.0 | 4 / 19 | |
| 1.8.1 | 4 / 19 | |
| 1.8.0 | 4 / 19 | |
| 1.7.0 | 4 / 19 | |
| 1.6.4 | 4 / 19 | |
| 1.6.3 | 4 / 19 | |
| 1.6.2 | 4 / 19 | |
| 1.6.1 | 4 / 19 | |
| 1.6.0 | 4 / 19 | |
| 1.5.0 | 4 / 19 | |
| 1.4.0 | 4 / 19 | |
| 1.3.2 | 4 / 19 | |
| 1.3.1 | 4 / 19 | |
| 1.3.0 | 4 / 19 | |
| 1.2.1 | 4 / 19 | |
| 1.2.0 | 4 / 19 | |
| 1.1.0 | 4 / 19 | |
| 1.0.0 | 4 / 14 |
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.