head to head · open source
sharp vs PermissionsKit
sharp has 32,817 GitHub stars, 1,447 forks, 123 open issues and last shipped 5 days ago. PermissionsKit has 5,811 stars, 479 forks, 4 open issues and last shipped 2 months ago. sharp leads on adoption by 465% (32,817 vs 5,811 stars). sharp is written in JavaScript under Apache-2.0; PermissionsKit is written in Swift under MIT. sharp has attracted 4% as many forks as stars, PermissionsKit 8%. sharp was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| sharp | PermissionsKit | |
|---|---|---|
| GitHub stars | ★ 33K | ★ 5.8K |
| License | Apache-2.0 | MIT |
| Written in | JavaScript | Swift |
| Last push | 2026-10-29 | 2026-09-12 |
| Forks | ⑂ 1.4K | ⑂ 479 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick sharp if
- You weight community size — 33K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches JavaScript
- You value the larger contributor base for long-term maintenance
pick PermissionsKit if
- You want the PermissionsKit feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Swift
- You evaluated both and PermissionsKit fits your workflow better
About sharp
sharp The typical use case for this high speed Node API module is to convert large images in common formats to smaller, web friendly JPEG, PNG, WebP, GIF and AVIF images of varying dimensions. It can be used with all JavaScript runtimes that provide support for Node API v9, including Node.js ( = 20.9.0), Deno and Bun. Resizing an image is typically 4x 5x faster than using the quickest ImageMagick and GraphicsMagick settings due to its use of libvips. Colour spaces, embedded ICC profiles and alpha transparency channels are all handled correctly. Lanczos resampling ensures quality is not sacrificed for speed. As…
read the full sharp overview →
About PermissionsKit
PermissionsKit Universal API for requesting permissions and reading their status — .authorized , .denied & .notDetermined . Each permission ships as a separate product, so the app compiles only the ones it actually uses. Installation In Xcode: File → Add Package Dependencies → paste URL: Then pick the products you need. Add only those — every permission API you link is visible to App Review, and unused ones invite questions about why the app needs them. Permissions Usage Request a permission: Read its status: [!WARNING] FaceID can't tell .authorized from .notDetermined — both come back as .notDetermined . Only…
read the full PermissionsKit overview →
More in Miscellaneous
Related comparisons
More Photo & Video Editors projects
Compare either of these against the rest of the Photo & Video Editors field.
Frequently asked questions
Is sharp or PermissionsKit more popular?
sharp has 32,817 GitHub stars and PermissionsKit has 5,811. sharp has the larger community by that measure.
Are sharp and PermissionsKit free?
Both are open source. sharp is licensed under Apache-2.0 and PermissionsKit under MIT. Neither carries a licence fee.
What is the difference between sharp and PermissionsKit?
sharp is written in JavaScript and PermissionsKit in Swift. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, sharp or PermissionsKit?
Choose sharp if you want the larger community (32,817 stars) or its Apache-2.0 licence terms. Choose PermissionsKit if its feature set, stack or MIT licence fits better. Both are self-hostable.