Adaptation of the original PdfViewer app to work as a library (fork of https://github.com/GrapheneOS/PdfViewer)
Go to file
June 9596bcf082 add pdfjs-dist submodule and symlink minified files
This should make the update process of pdf.js far easier and more maintainable as we can just use the pdfjs-dist tags

Signed-off-by: June <june@eridan.me>
2022-01-22 22:12:31 -05:00
.github cleaner style for validate gradle wrapper action 2021-11-29 23:40:33 -05:00
app add pdfjs-dist submodule and symlink minified files 2022-01-22 22:12:31 -05:00
gradle/wrapper update gradle to 7.3.3 2021-12-26 16:16:41 -05:00
third_party add pdfjs-dist submodule and symlink minified files 2022-01-22 22:12:31 -05:00
.gitignore use Gradle Kotlin DSL 2021-11-21 15:10:47 -05:00
.gitmodules add pdfjs-dist submodule and symlink minified files 2022-01-22 22:12:31 -05:00
LICENSE update copyright notice 2021-11-11 22:20:55 -05:00
PDFJS_LICENSE initial commit with overhauled / rebranded project 2019-06-27 23:22:08 -04:00
README.md add README based on release notes 2020-05-27 19:11:43 -04:00
build.gradle.kts Bump kotlin-gradle-plugin from 1.6.0 to 1.6.10 2021-12-14 16:27:48 -05:00
gradle.properties disable obsolete jetifier 2021-11-21 16:55:27 -05:00
gradlew update gradle to 7.2 2021-08-21 00:09:49 -04:00
gradlew.bat update gradle wrapper 2020-11-09 22:08:13 -05:00
settings.gradle.kts use Gradle Kotlin DSL 2021-11-21 15:10:47 -05:00

README.md

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.