← nur  /  sdk census  /  Bugsnag
Error/Crash Monitoring
8 of 320 sampled app binaries

Bugsnag code is detected in 8 binaries in nur’s static, alphabetical July 21, 2026 sample. Presence does not establish use.

In 4 of those apps, Bugsnag ships alongside another Error/Crash Monitoring vendor in the same binary. This is co-residence only; a dated snapshot cannot show whether it reflects migration, evaluation, redundancy, or use. Which apps? That’s in the gated view.

🔒

See the specific binaries containing Bugsnag, their other fingerprinted SDKs, and the same-category co-residence map.

Register free for app-level access For vendors: request access

Others in Error/Crash Monitoring

Firebase Crashlytics61 apps
Sentry40 apps
nur reports neutral, dated facts about SDK code detected in a static sample of 320 public app binaries read July 21, 2026. The crawl is alphabetical, not a representative sample. Presence does not establish use, configuration, effectiveness, endorsement, or migration. This is not a security rating, ranking, or recommendation. Vendor names are used nominatively. No DRM was circumvented. See an error? Flag it.