npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@njweber/privacy-check

v0.1.1

Published

Check which privacy-sensitive iOS APIs an app uses and whether every required usage-description key is declared — dependency-free.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

njwebernjweber

Keywords

iosapp-storeprivacyinfo-plistusage-descriptionreact-nativeexporeleasesubmission

Readme

privacy-check

npm downloads CI

Catch a missing iOS privacy usage description before App Store review does. privacy-check scans the app binary for privacy-sensitive APIs, then checks that every required Info.plist key is declared.

npx @njweber/privacy-check ./build/YourApp.ipa

--help prints usage; --version prints the installed version.

privacy-check — iOS privacy usage audit
artifact: ./build/YourApp.ipa

✓ binary  scanned Demo
✓ NSCameraUsageDescription  camera used (AVCaptureDevice); NSCameraUsageDescription declared
✗ NSUserTrackingUsageDescription  tracking (App Tracking Transparency) used (ATTrackingManager) but
    NSUserTrackingUsageDescription is MISSING — the app will crash on first use and the build will be rejected

FAIL — 1 blocking issue.

Why

Missing usage-description keys are one of the most common App Store rejections and a guaranteed runtime crash the moment the API is touched. They're trivial to check and easy to overlook — especially in React Native / Expo apps where a dependency pulls in the API, not your own code.

What it maps

| API detected in the binary | Required Info.plist key | |---|---| | AVCaptureDevice / AVCaptureSession | NSCameraUsageDescription | | AVAudioRecorder | NSMicrophoneUsageDescription | | PHPhotoLibrary / UIImagePickerController | NSPhotoLibraryUsageDescription | | CLLocationManager | NSLocationWhenInUseUsageDescription | | CNContactStore | NSContactsUsageDescription | | EKEventStore | NSCalendarsUsageDescription | | CMMotionManager / CMPedometer | NSMotionUsageDescription | | SFSpeechRecognizer | NSSpeechRecognitionUsageDescription | | HKHealthStore | NSHealthShareUsageDescription | | MPMediaLibrary | NSAppleMusicUsageDescription | | ATTrackingManager | NSUserTrackingUsageDescription | | CBCentralManager / CBPeripheralManager | NSBluetoothAlwaysUsageDescription | | LAContext | NSFaceIDUsageDescription (warn) | | NWBrowser / NetService | NSLocalNetworkUsageDescription (warn) |

It also flags declared-but-unused keys.

Honest limits

It's a heuristic: it looks for API symbols in the binary. A symbol can be linked without the code path being reachable (false positive → an extra warning), and a statically-analysed call can hide (false negative). Treat it as a fast pre-flight, not a legal audit.

Exit codes

0 clean · 1 blocking issue(s) · 2 bad input.

Family

app-check · store-check · ipa-check · icon-check

Follow along

More of this at https://booleanbuild.com — the tools hub, plus write-ups on store rejections, CI, build gates, and shipping TestFlight builds without EAS. New posts land roughly twice a month. Subscribe: https://booleanbuild.com/#subscribe

License

MIT.