Adaptation of the original PdfViewer app to work as a library (fork of https://github.com/GrapheneOS/PdfViewer)
Go to file
dependabot[bot] fb28446727 Bump actions/checkout from 3 to 4
Bumps [actions/checkout](https://github.com/actions/checkout) from 3 to 4.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](https://github.com/actions/checkout/compare/v3...v4)

---
updated-dependencies:
- dependency-name: actions/checkout
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
2023-09-05 03:37:57 -04:00
.github Bump actions/checkout from 3 to 4 2023-09-05 03:37:57 -04:00
app update SDK to 34 (Android 14) 2023-08-25 18:31:25 -04:00
gradle update Android Gradle plugin to 8.1.1 2023-08-25 18:30:27 -04:00
.eslintrc.json add eslint config and missing semicolons 2023-06-09 11:33:53 -04:00
.gitignore migrate to pdfjs-dist npm package 2023-03-24 19:45:49 -04:00
LICENSE update copyright notice 2023-02-01 23:37:39 -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 update Android Gradle plugin to 8.1.1 2023-08-25 18:30:27 -04:00
gradle.properties update Android Gradle Plugin to 8.0.0 2023-04-14 08:37:42 -04:00
gradlew update Gradle to 8.3 2023-08-17 13:00:29 -04:00
gradlew.bat update Gradle to 7.6 2022-12-09 08:48:17 -05:00
package-lock.json Bump eslint from 8.47.0 to 8.48.0 2023-08-25 18:01:52 -04:00
package.json Bump eslint from 8.47.0 to 8.48.0 2023-08-25 18:01:52 -04:00
settings.gradle.kts Update Gradle build scripts 2023-05-03 12:58:19 -04:00
setup add setup script 2023-03-24 19:46:52 -04: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.