Adaptation of the original PdfViewer app to work as a library (fork of https://github.com/GrapheneOS/PdfViewer)
Go to file
2024-02-11 10:59:50 -05:00
.github Bump gradle/wrapper-validation-action from 1 to 2 2024-01-29 16:20:53 -05:00
app update Material Components library to 1.11.0 2023-12-25 11:40:37 -05:00
gradle update Gradle to 8.6 2024-02-11 10:59:50 -05:00
viewer update worker import for PDF.js v4 2024-02-05 01:03:54 -05:00
.eslintrc.json viewer: use esbuild to bundle pdf viewer and worker 2023-09-16 04:20:38 -04:00
.gitignore viewer: use esbuild to bundle pdf viewer and worker 2023-09-16 04:20:38 -04:00
build.gradle.kts update Android Gradle plugin to 8.2.1 2024-01-09 15:58:14 -05:00
gradle.properties update Android Gradle Plugin to 8.0.0 2023-04-14 08:37:42 -04:00
gradlew update Gradle to 8.4 2023-11-12 17:51:46 -05:00
gradlew.bat update Gradle to 8.6 2024-02-11 10:59:50 -05:00
LICENSE update copyright notice 2023-02-01 23:37:39 -05:00
package-lock.json Bump pdfjs-dist from 3.11.174 to 4.0.379 2024-02-05 01:03:54 -05:00
package.json Bump pdfjs-dist from 3.11.174 to 4.0.379 2024-02-05 01:03:54 -05:00
PDFJS_LICENSE initial commit with overhauled / rebranded project 2019-06-27 23:22:08 -04:00
process_static.js viewer: use esbuild to bundle pdf viewer and worker 2023-09-16 04:20:38 -04:00
README.md add README based on release notes 2020-05-27 19:11:43 -04:00
settings.gradle.kts Update Gradle build scripts 2023-05-03 12:58:19 -04:00

Simple Android PDF viewer based on pdf.js and content providers. The app doesn't require any permissions. The PDF stream is fed into the sandboxed WebView without giving it access to content or files. Content-Security-Policy is used to enforce that the JavaScript and styling properties within the WebView are entirely static content from the apk assets. It reuses the hardened Chromium rendering stack while only exposing a tiny subset of the attack surface compared to actual web content. The PDF rendering code itself is memory safe with dynamic code evaluation disabled, and even if an attacker did gain code execution by exploiting the underlying web rendering engine, they're within the Chromium renderer sandbox with no access to the network (unlike a browser), files, or other content.