Executive summary
TheWidlarzGroup/react-native-video is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because we found no logging, tracing or health checks in the code. It scores 55 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 43, is the weakest lens and counts most in the score. The best first step is adopting a logging library, worth about 7 points. Adding automated security scanning comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 65.
Sixty-six known security holes in the packages the code depends on can be used by attackers. Twenty-eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Updating the vulnerable packages and pinning each tool to an exact version would close both risks. Passing outside input through environment variables would fix the four pipeline steps that put outside input straight into a shell command, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The two test suites that won't install need their lockfile updated so they install.
The product code is 16,096 lines, about €21,000 to rebuild.
If Production Readiness rose from 43 to 70, the lowest score rated Strong, the score would rise from 55 to about 65.
New since the last survey: 82 findings
- Code Duplication · Edited copy of a member (40 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift
- Code Duplication · Edited copy of a member (40 corresponding lines) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt
- Code Duplication · Edited copy of a member (23 corresponding lines) packages/react-native-video/ios/view/VideoComponentViewObserver.swift
- Code Duplication · Edited copy of a member (12 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerSource/SourceLoader.swift
- Code Duplication · Edited copy of a member (7 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (13 corresponding lines) packages/react-native-video/android/src/main/java/com/twg/video/view/VideoView.kt
- Code Duplication · Edited copy of a member (14 corresponding lines) packages/react-native-video/ios/core/VideoManager.swift
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift
- Code Duplication · Edited copy of a member (13 corresponding lines) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/PictureInPictureUtils.kt
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Duplicated block (13 lines × 2) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Code Duplication · Duplicated block (9 lines × 2) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Hygiene · Unused dependency '@octokit/rest'
- Dependency Hygiene · Unused dependency '@release-it/bumper'
- Dependency Hygiene · Unused dependency '@release-it/conventional-changelog'
- Dependency Hygiene · Unused dependency 'conventional-changelog-conventionalcommits'
- Dependency Hygiene · Unused dependency '@react-native-community/cli-platform-android'
- Dependency Hygiene · Unused dependency '@react-native-community/cli-platform-ios'
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/expo-plugins/getPackageInfo.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/expo-plugins/getPackageInfo.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts
Fixed since the last survey: 37 findings
- Code Duplication · Duplicated block (13 lines × 2) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift
- Secret Scanning · Leaked secret: jwt example/src/utils/videoSource.ts
- Secret Scanning · Leaked secret: private-key-store example/android/app/debug.keystore
- Churn × Complexity Hotspots · Hotspot: test-app/src/e2e/eventLog.ts test-app/src/e2e/eventLog.ts
- Secrets (history) · High secret: WD-SECRET-0004 example/android/app/debug.keystore
- Secrets (history) · Secret: jwt example/src/utils/videoSource.ts
- Secrets (history) · High secret: WD-SECRET-0005 examples/FabricExample/src/VideoPlayer.tsx
- Secrets (history) · High secret: WD-SECRET-0005 examples/bare/src/constants/general.ts
- Secrets (history) · High secret: WD-SECRET-0005 examples/basic/src/VideoPlayer.tsx
- Secrets (history) · High secret: WD-SECRET-0005 examples/basic/src/constants/general.ts
- Secrets (history) · High secret: WD-SECRET-0005 examples/common/constants/general.ts
- Secrets (history) · High secret: WD-SECRET-0005 examples/expo/src/constants/general.ts
- Static Analysis (SAST) · Medium: watchdog-regexp-from-parameter-ts scripts/e2e/junit-summary.mjs
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Import Boundaries · Boundary violation [package:relative-cross-package] packages/react-native-video/src/expo-plugins/getPackageInfo.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/expo-plugins/getPackageInfo.ts
- Exception handling · Swallowed exception (empty catch) packages/react-native-video/src/expo-plugins/getPackageInfo.ts
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €7,000 to €35,000, for 117 to 371 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 16,096 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 androidx.media3.exoplayer.dash.manifest | 2 com.twg.video.core.services.playback.CustomMediaNotificationProvider.Companion | 3 com.twg.video.core.services.playback.VideoPlaybackServiceConnection | 4 packages.react-native-video.src.core.types.EventEmitter | 5 packages.react-native-video.src.core.types.IgnoreSilentSwitchMode | 6 packages.react-native-video.src.core.types.MixAudioMode | 7 packages.react-native-video.src.core.types.VideoOrientation | 8 packages.react-native-video.src.core.types.VideoPlayerStatus | 9 packages.react-native-video.src.core.types.WebVideoPlayer | 10 packages.react-native-video.src.core.web.WebMediaProxy | 11 androidx.media3.exoplayer.dash | 12 com.twg.video.core.player | 13 com.twg.video.core.recivers | 14 com.twg.video.core.services.playback | 15 com.twg.video.view | 16 packages.react-native-video.src.core.events.VideoPlayerEventsBase | 17 packages.react-native-video.src.core.types.VideoInformation | 18 packages.react-native-video.src.core.web.WebEventEmitter | 19 com.twg.video.core.extensions | 20 com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState | 21 com.twg.video.core.utils | 22 packages.react-native-video.src.core.events.VideoPlayerEvents_native | 23 packages.react-native-video.src.core.events.VideoPlayerEvents_web | 24 packages.react-native-video.src.core.types.VideoPlayerSourceBase | 25 com.margelo.nitro.video | 26 packages.react-native-video.src.core.types.Events | 27 packages.react-native-video.src.core.types.VideoPlayerBase | 28 com.twg.video.core | 29 com.twg.video.core.plugins | 30 com.twg.videodrm.DRMManager | 31 packages.react-native-video.src.core.VideoPlayer | 32 packages.react-native-video.src.core.VideoPlayer_web | 33 packages.react-native-video.src.core.video-view.VideoViewProps | 34 com.twg.video.core.LibraryError | 35 com.twg.video.core.PlayerError | 36 com.twg.video.core.SourceError | 37 com.twg.video.core.VideoViewError | 38 com.twg.videodrm | 39 packages.react-native-video.src.core.video-view | 40 com.margelo.nitro.videodrm |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 androidx.media3.exoplayer.dash.manifest | ||||||||||||||||||||||||||||||||||||||||
| 2 com.twg.video.core.services.playback.CustomMediaNotificationProvider.Companion | ||||||||||||||||||||||||||||||||||||||||
| 3 com.twg.video.core.services.playback.VideoPlaybackServiceConnection | ||||||||||||||||||||||||||||||||||||||||
| 4 packages.react-native-video.src.core.types.EventEmitter | ||||||||||||||||||||||||||||||||||||||||
| 5 packages.react-native-video.src.core.types.IgnoreSilentSwitchMode | ||||||||||||||||||||||||||||||||||||||||
| 6 packages.react-native-video.src.core.types.MixAudioMode | ||||||||||||||||||||||||||||||||||||||||
| 7 packages.react-native-video.src.core.types.VideoOrientation | ||||||||||||||||||||||||||||||||||||||||
| 8 packages.react-native-video.src.core.types.VideoPlayerStatus | ||||||||||||||||||||||||||||||||||||||||
| 9 packages.react-native-video.src.core.types.WebVideoPlayer | ||||||||||||||||||||||||||||||||||||||||
| 10 packages.react-native-video.src.core.web.WebMediaProxy | ||||||||||||||||||||||||||||||||||||||||
| 11 androidx.media3.exoplayer.dash | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 com.twg.video.core.player | 3 | |||||||||||||||||||||||||||||||||||||||
| 13 com.twg.video.core.recivers | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 com.twg.video.core.services.playback | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 15 com.twg.video.view | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 packages.react-native-video.src.core.events.VideoPlayerEventsBase | 2 | |||||||||||||||||||||||||||||||||||||||
| 17 packages.react-native-video.src.core.types.VideoInformation | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 packages.react-native-video.src.core.web.WebEventEmitter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 com.twg.video.core.extensions | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 com.twg.video.core.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 packages.react-native-video.src.core.events.VideoPlayerEvents_native | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 packages.react-native-video.src.core.events.VideoPlayerEvents_web | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 packages.react-native-video.src.core.types.VideoPlayerSourceBase | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 com.margelo.nitro.video | 2 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 26 packages.react-native-video.src.core.types.Events | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 packages.react-native-video.src.core.types.VideoPlayerBase | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 com.twg.video.core | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 29 com.twg.video.core.plugins | 3 | 3 | 6 | |||||||||||||||||||||||||||||||||||||
| 30 com.twg.videodrm.DRMManager | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 packages.react-native-video.src.core.VideoPlayer | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 32 packages.react-native-video.src.core.VideoPlayer_web | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 33 packages.react-native-video.src.core.video-view.VideoViewProps | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 com.twg.video.core.LibraryError | 4 | |||||||||||||||||||||||||||||||||||||||
| 35 com.twg.video.core.PlayerError | 5 | |||||||||||||||||||||||||||||||||||||||
| 36 com.twg.video.core.SourceError | 6 | |||||||||||||||||||||||||||||||||||||||
| 37 com.twg.video.core.VideoViewError | 3 | |||||||||||||||||||||||||||||||||||||||
| 38 com.twg.videodrm | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 packages.react-native-video.src.core.video-view | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 com.margelo.nitro.videodrm | 1 |
11→1 androidx.media3.exoplayer.dash uses androidx.media3.exoplayer.dash.manifest✕
- Connections
- 1 pair of types, where a type in androidx.media3.exoplayer.dash uses a type in androidx.media3.exoplayer.dash.manifest.
- The types involved
androidx.media3.exoplayer.dash.DashUtil→androidx.media3.exoplayer.dash.manifest.DashManifest
- Direction
- androidx.media3.exoplayer.dash uses androidx.media3.exoplayer.dash.manifest, so a change to androidx.media3.exoplayer.dash.manifest can break androidx.media3.exoplayer.dash, while a change to androidx.media3.exoplayer.dash can't break androidx.media3.exoplayer.dash.manifest.
- Position
- Below the diagonal: androidx.media3.exoplayer.dash uses a module listed above it, which is the healthy direction.
12→25 com.twg.video.core.player uses com.margelo.nitro.video part of a loop✕
- Connections
- 3 pairs of types, where a type in com.twg.video.core.player uses a type in com.margelo.nitro.video.
- The types involved
com.twg.video.core.player.MediaItemUtilsKt→com.margelo.nitro.video.HybridVideoPlayerSourcecom.twg.video.core.player.MediaSourceUtilsKt→com.margelo.nitro.video.HybridVideoPlayerSourcecom.twg.video.core.player.OnAudioFocusChangedListener→com.margelo.nitro.video.HybridVideoPlayerEventEmitter
- Direction
- com.twg.video.core.player uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.video.core.player, while a change to com.twg.video.core.player can't break com.margelo.nitro.video.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→25 com.twg.video.core.recivers uses com.margelo.nitro.video part of a loop✕
- Connections
- 1 pair of types, where a type in com.twg.video.core.recivers uses a type in com.margelo.nitro.video.
- The types involved
com.twg.video.core.recivers.AudioBecomingNoisyReceiver→com.margelo.nitro.video.HybridVideoPlayerEventEmitter
- Direction
- com.twg.video.core.recivers uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.video.core.recivers, while a change to com.twg.video.core.recivers can't break com.margelo.nitro.video.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 com.twg.video.core.services.playback uses com.twg.video.core.services.playback.VideoPlaybackServiceConnection✕
- Connections
- 1 pair of types, where a type in com.twg.video.core.services.playback uses a type in com.twg.video.core.services.playback.VideoPlaybackServiceConnection.
- The types involved
com.twg.video.core.services.playback.VideoPlaybackServiceConnection→com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState
- Direction
- com.twg.video.core.services.playback uses com.twg.video.core.services.playback.VideoPlaybackServiceConnection, so a change to com.twg.video.core.services.playback.VideoPlaybackServiceConnection can break com.twg.video.core.services.playback, while a change to com.twg.video.core.services.playback can't break com.twg.video.core.services.playback.VideoPlaybackServiceConnection.
- Position
- Below the diagonal: com.twg.video.core.services.playback uses a module listed above it, which is the healthy direction.
14→25 com.twg.video.core.services.playback uses com.margelo.nitro.video part of a loop✕
- Connections
- 2 pairs of types, where a type in com.twg.video.core.services.playback uses a type in com.margelo.nitro.video.
- The types involved
com.twg.video.core.services.playback.VideoPlaybackService→com.margelo.nitro.video.HybridVideoPlayercom.twg.video.core.services.playback.VideoPlaybackServiceConnection→com.margelo.nitro.video.HybridVideoPlayer
- Direction
- com.twg.video.core.services.playback uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.video.core.services.playback, while a change to com.twg.video.core.services.playback can't break com.margelo.nitro.video.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→25 com.twg.video.view uses com.margelo.nitro.video part of a loop✕
- Connections
- 2 pairs of types, where a type in com.twg.video.view uses a type in com.margelo.nitro.video.
- The types involved
com.twg.video.view.VideoView→com.margelo.nitro.video.HybridVideoPlayercom.twg.video.view.VideoView→com.margelo.nitro.video.VideoViewEventsEmitter
- Direction
- com.twg.video.view uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.video.view, while a change to com.twg.video.view can't break com.margelo.nitro.video.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→4 packages.react-native-video.src.core.events.VideoPlayerEventsBase uses packages.react-native-video.src.core.types.EventEmitter✕
- Connections
- 2 pairs of types, where a type in packages.react-native-video.src.core.events.VideoPlayerEventsBase uses a type in packages.react-native-video.src.core.types.EventEmitter.
- The types involved
packages.react-native-video.src.core.events.VideoPlayerEventsBase.VideoPlayerEventsBase→packages.react-native-video.src.core.types.EventEmitter.ListenerSubscriptionpackages.react-native-video.src.core.events.VideoPlayerEventsBase.VideoPlayerEventsBase→packages.react-native-video.src.core.types.EventEmitter.VideoPlayerEventEmitterBase
- Direction
- packages.react-native-video.src.core.events.VideoPlayerEventsBase uses packages.react-native-video.src.core.types.EventEmitter, so a change to packages.react-native-video.src.core.types.EventEmitter can break packages.react-native-video.src.core.events.VideoPlayerEventsBase, while a change to packages.react-native-video.src.core.events.VideoPlayerEventsBase can't break packages.react-native-video.src.core.types.EventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.events.VideoPlayerEventsBase uses a module listed above it, which is the healthy direction.
17→7 packages.react-native-video.src.core.types.VideoInformation uses packages.react-native-video.src.core.types.VideoOrientation✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoInformation uses a type in packages.react-native-video.src.core.types.VideoOrientation.
- The types involved
packages.react-native-video.src.core.types.VideoInformation.VideoInformation→packages.react-native-video.src.core.types.VideoOrientation.VideoOrientation
- Direction
- packages.react-native-video.src.core.types.VideoInformation uses packages.react-native-video.src.core.types.VideoOrientation, so a change to packages.react-native-video.src.core.types.VideoOrientation can break packages.react-native-video.src.core.types.VideoInformation, while a change to packages.react-native-video.src.core.types.VideoInformation can't break packages.react-native-video.src.core.types.VideoOrientation.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoInformation uses a module listed above it, which is the healthy direction.
18→4 packages.react-native-video.src.core.web.WebEventEmitter uses packages.react-native-video.src.core.types.EventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.web.WebEventEmitter uses a type in packages.react-native-video.src.core.types.EventEmitter.
- The types involved
packages.react-native-video.src.core.web.WebEventEmitter.WebEventEmitter→packages.react-native-video.src.core.types.EventEmitter.ListenerSubscription
- Direction
- packages.react-native-video.src.core.web.WebEventEmitter uses packages.react-native-video.src.core.types.EventEmitter, so a change to packages.react-native-video.src.core.types.EventEmitter can break packages.react-native-video.src.core.web.WebEventEmitter, while a change to packages.react-native-video.src.core.web.WebEventEmitter can't break packages.react-native-video.src.core.types.EventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.web.WebEventEmitter uses a module listed above it, which is the healthy direction.
18→10 packages.react-native-video.src.core.web.WebEventEmitter uses packages.react-native-video.src.core.web.WebMediaProxy✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.web.WebEventEmitter uses a type in packages.react-native-video.src.core.web.WebMediaProxy.
- The types involved
packages.react-native-video.src.core.web.WebEventEmitter.WebEventEmitter→packages.react-native-video.src.core.web.WebMediaProxy.WebMediaProxy
- Direction
- packages.react-native-video.src.core.web.WebEventEmitter uses packages.react-native-video.src.core.web.WebMediaProxy, so a change to packages.react-native-video.src.core.web.WebMediaProxy can break packages.react-native-video.src.core.web.WebEventEmitter, while a change to packages.react-native-video.src.core.web.WebEventEmitter can't break packages.react-native-video.src.core.web.WebMediaProxy.
- Position
- Below the diagonal: packages.react-native-video.src.core.web.WebEventEmitter uses a module listed above it, which is the healthy direction.
19→14 com.twg.video.core.extensions uses com.twg.video.core.services.playback✕
- Connections
- 1 pair of types, where a type in com.twg.video.core.extensions uses a type in com.twg.video.core.services.playback.
- The types involved
com.twg.video.core.extensions.VideoPlaybackService+ServiceManagmentKt→com.twg.video.core.services.playback.VideoPlaybackServiceConnection
- Direction
- com.twg.video.core.extensions uses com.twg.video.core.services.playback, so a change to com.twg.video.core.services.playback can break com.twg.video.core.extensions, while a change to com.twg.video.core.extensions can't break com.twg.video.core.services.playback.
- Position
- Below the diagonal: com.twg.video.core.extensions uses a module listed above it, which is the healthy direction.
20→3 com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses com.twg.video.core.services.playback.VideoPlaybackServiceConnection✕
- Connections
- 3 pairs of types, where a type in com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses a type in com.twg.video.core.services.playback.VideoPlaybackServiceConnection.
- The types involved
com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState.Binding→com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionStatecom.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState.Connected→com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionStatecom.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState.Disconnected→com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState
- Direction
- com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses com.twg.video.core.services.playback.VideoPlaybackServiceConnection, so a change to com.twg.video.core.services.playback.VideoPlaybackServiceConnection can break com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState, while a change to com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState can't break com.twg.video.core.services.playback.VideoPlaybackServiceConnection.
- Position
- Below the diagonal: com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses a module listed above it, which is the healthy direction.
20→14 com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses com.twg.video.core.services.playback✕
- Connections
- 1 pair of types, where a type in com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses a type in com.twg.video.core.services.playback.
- The types involved
com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState.Connected→com.twg.video.core.services.playback.VideoPlaybackServiceBinder
- Direction
- com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses com.twg.video.core.services.playback, so a change to com.twg.video.core.services.playback can break com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState, while a change to com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState can't break com.twg.video.core.services.playback.
- Position
- Below the diagonal: com.twg.video.core.services.playback.VideoPlaybackServiceConnection.ConnectionState uses a module listed above it, which is the healthy direction.
21→15 com.twg.video.core.utils uses com.twg.video.view✕
- Connections
- 1 pair of types, where a type in com.twg.video.core.utils uses a type in com.twg.video.view.
- The types involved
com.twg.video.core.utils.PictureInPictureUtils→com.twg.video.view.VideoView
- Direction
- com.twg.video.core.utils uses com.twg.video.view, so a change to com.twg.video.view can break com.twg.video.core.utils, while a change to com.twg.video.core.utils can't break com.twg.video.view.
- Position
- Below the diagonal: com.twg.video.core.utils uses a module listed above it, which is the healthy direction.
22→4 packages.react-native-video.src.core.events.VideoPlayerEvents_native uses packages.react-native-video.src.core.types.EventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.events.VideoPlayerEvents_native uses a type in packages.react-native-video.src.core.types.EventEmitter.
- The types involved
packages.react-native-video.src.core.events.VideoPlayerEvents_native.VideoPlayerEvents→packages.react-native-video.src.core.types.EventEmitter.ListenerSubscription
- Direction
- packages.react-native-video.src.core.events.VideoPlayerEvents_native uses packages.react-native-video.src.core.types.EventEmitter, so a change to packages.react-native-video.src.core.types.EventEmitter can break packages.react-native-video.src.core.events.VideoPlayerEvents_native, while a change to packages.react-native-video.src.core.events.VideoPlayerEvents_native can't break packages.react-native-video.src.core.types.EventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.events.VideoPlayerEvents_native uses a module listed above it, which is the healthy direction.
22→16 packages.react-native-video.src.core.events.VideoPlayerEvents_native uses packages.react-native-video.src.core.events.VideoPlayerEventsBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.events.VideoPlayerEvents_native uses a type in packages.react-native-video.src.core.events.VideoPlayerEventsBase.
- The types involved
packages.react-native-video.src.core.events.VideoPlayerEvents_native.VideoPlayerEvents→packages.react-native-video.src.core.events.VideoPlayerEventsBase.VideoPlayerEventsBase
- Direction
- packages.react-native-video.src.core.events.VideoPlayerEvents_native uses packages.react-native-video.src.core.events.VideoPlayerEventsBase, so a change to packages.react-native-video.src.core.events.VideoPlayerEventsBase can break packages.react-native-video.src.core.events.VideoPlayerEvents_native, while a change to packages.react-native-video.src.core.events.VideoPlayerEvents_native can't break packages.react-native-video.src.core.events.VideoPlayerEventsBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.events.VideoPlayerEvents_native uses a module listed above it, which is the healthy direction.
23→4 packages.react-native-video.src.core.events.VideoPlayerEvents_web uses packages.react-native-video.src.core.types.EventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.events.VideoPlayerEvents_web uses a type in packages.react-native-video.src.core.types.EventEmitter.
- The types involved
packages.react-native-video.src.core.events.VideoPlayerEvents_web.VideoPlayerEvents→packages.react-native-video.src.core.types.EventEmitter.ListenerSubscription
- Direction
- packages.react-native-video.src.core.events.VideoPlayerEvents_web uses packages.react-native-video.src.core.types.EventEmitter, so a change to packages.react-native-video.src.core.types.EventEmitter can break packages.react-native-video.src.core.events.VideoPlayerEvents_web, while a change to packages.react-native-video.src.core.events.VideoPlayerEvents_web can't break packages.react-native-video.src.core.types.EventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.events.VideoPlayerEvents_web uses a module listed above it, which is the healthy direction.
23→16 packages.react-native-video.src.core.events.VideoPlayerEvents_web uses packages.react-native-video.src.core.events.VideoPlayerEventsBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.events.VideoPlayerEvents_web uses a type in packages.react-native-video.src.core.events.VideoPlayerEventsBase.
- The types involved
packages.react-native-video.src.core.events.VideoPlayerEvents_web.VideoPlayerEvents→packages.react-native-video.src.core.events.VideoPlayerEventsBase.VideoPlayerEventsBase
- Direction
- packages.react-native-video.src.core.events.VideoPlayerEvents_web uses packages.react-native-video.src.core.events.VideoPlayerEventsBase, so a change to packages.react-native-video.src.core.events.VideoPlayerEventsBase can break packages.react-native-video.src.core.events.VideoPlayerEvents_web, while a change to packages.react-native-video.src.core.events.VideoPlayerEvents_web can't break packages.react-native-video.src.core.events.VideoPlayerEventsBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.events.VideoPlayerEvents_web uses a module listed above it, which is the healthy direction.
24→17 packages.react-native-video.src.core.types.VideoPlayerSourceBase uses packages.react-native-video.src.core.types.VideoInformation✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoPlayerSourceBase uses a type in packages.react-native-video.src.core.types.VideoInformation.
- The types involved
packages.react-native-video.src.core.types.VideoPlayerSourceBase.VideoPlayerSourceBase→packages.react-native-video.src.core.types.VideoInformation.VideoInformation
- Direction
- packages.react-native-video.src.core.types.VideoPlayerSourceBase uses packages.react-native-video.src.core.types.VideoInformation, so a change to packages.react-native-video.src.core.types.VideoInformation can break packages.react-native-video.src.core.types.VideoPlayerSourceBase, while a change to packages.react-native-video.src.core.types.VideoPlayerSourceBase can't break packages.react-native-video.src.core.types.VideoInformation.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoPlayerSourceBase uses a module listed above it, which is the healthy direction.
25→12 com.margelo.nitro.video uses com.twg.video.core.player✕
- Connections
- 2 pairs of types, where a type in com.margelo.nitro.video uses a type in com.twg.video.core.player.
- The types involved
com.margelo.nitro.video.HybridVideoPlayer→com.twg.video.core.player.OnAudioFocusChangedListenercom.margelo.nitro.video.HybridVideoPlayerSource→com.twg.video.core.player.DRMManagerSpec
- Direction
- com.margelo.nitro.video uses com.twg.video.core.player, so a change to com.twg.video.core.player can break com.margelo.nitro.video, while a change to com.margelo.nitro.video can't break com.twg.video.core.player.
- Position
- Below the diagonal: com.margelo.nitro.video uses a module listed above it, which is the healthy direction.
25→13 com.margelo.nitro.video uses com.twg.video.core.recivers✕
- Connections
- 1 pair of types, where a type in com.margelo.nitro.video uses a type in com.twg.video.core.recivers.
- The types involved
com.margelo.nitro.video.HybridVideoPlayer→com.twg.video.core.recivers.AudioBecomingNoisyReceiver
- Direction
- com.margelo.nitro.video uses com.twg.video.core.recivers, so a change to com.twg.video.core.recivers can break com.margelo.nitro.video, while a change to com.margelo.nitro.video can't break com.twg.video.core.recivers.
- Position
- Below the diagonal: com.margelo.nitro.video uses a module listed above it, which is the healthy direction.
25→14 com.margelo.nitro.video uses com.twg.video.core.services.playback✕
- Connections
- 1 pair of types, where a type in com.margelo.nitro.video uses a type in com.twg.video.core.services.playback.
- The types involved
com.margelo.nitro.video.HybridVideoPlayer→com.twg.video.core.services.playback.VideoPlaybackServiceConnection
- Direction
- com.margelo.nitro.video uses com.twg.video.core.services.playback, so a change to com.twg.video.core.services.playback can break com.margelo.nitro.video, while a change to com.margelo.nitro.video can't break com.twg.video.core.services.playback.
- Position
- Below the diagonal: com.margelo.nitro.video uses a module listed above it, which is the healthy direction.
25→15 com.margelo.nitro.video uses com.twg.video.view✕
- Connections
- 2 pairs of types, where a type in com.margelo.nitro.video uses a type in com.twg.video.view.
- The types involved
com.margelo.nitro.video.HybridVideoPlayer→com.twg.video.view.VideoViewcom.margelo.nitro.video.HybridVideoViewViewManager→com.twg.video.view.VideoView
- Direction
- com.margelo.nitro.video uses com.twg.video.view, so a change to com.twg.video.view can break com.margelo.nitro.video, while a change to com.margelo.nitro.video can't break com.twg.video.view.
- Position
- Below the diagonal: com.margelo.nitro.video uses a module listed above it, which is the healthy direction.
25→21 com.margelo.nitro.video uses com.twg.video.core.utils✕
- Connections
- 1 pair of types, where a type in com.margelo.nitro.video uses a type in com.twg.video.core.utils.
- The types involved
com.margelo.nitro.video.HybridVideoPlayerSource→com.twg.video.core.utils.SourceLoader
- Direction
- com.margelo.nitro.video uses com.twg.video.core.utils, so a change to com.twg.video.core.utils can break com.margelo.nitro.video, while a change to com.margelo.nitro.video can't break com.twg.video.core.utils.
- Position
- Below the diagonal: com.margelo.nitro.video uses a module listed above it, which is the healthy direction.
26→7 packages.react-native-video.src.core.types.Events uses packages.react-native-video.src.core.types.VideoOrientation✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.Events uses a type in packages.react-native-video.src.core.types.VideoOrientation.
- The types involved
packages.react-native-video.src.core.types.Events.onLoadData→packages.react-native-video.src.core.types.VideoOrientation.VideoOrientation
- Direction
- packages.react-native-video.src.core.types.Events uses packages.react-native-video.src.core.types.VideoOrientation, so a change to packages.react-native-video.src.core.types.VideoOrientation can break packages.react-native-video.src.core.types.Events, while a change to packages.react-native-video.src.core.types.Events can't break packages.react-native-video.src.core.types.VideoOrientation.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.Events uses a module listed above it, which is the healthy direction.
26→24 packages.react-native-video.src.core.types.Events uses packages.react-native-video.src.core.types.VideoPlayerSourceBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.Events uses a type in packages.react-native-video.src.core.types.VideoPlayerSourceBase.
- The types involved
packages.react-native-video.src.core.types.Events.onLoadStartData→packages.react-native-video.src.core.types.VideoPlayerSourceBase.VideoPlayerSourceBase
- Direction
- packages.react-native-video.src.core.types.Events uses packages.react-native-video.src.core.types.VideoPlayerSourceBase, so a change to packages.react-native-video.src.core.types.VideoPlayerSourceBase can break packages.react-native-video.src.core.types.Events, while a change to packages.react-native-video.src.core.types.Events can't break packages.react-native-video.src.core.types.VideoPlayerSourceBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.Events uses a module listed above it, which is the healthy direction.
27→4 packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.EventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoPlayerBase uses a type in packages.react-native-video.src.core.types.EventEmitter.
- The types involved
packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase→packages.react-native-video.src.core.types.EventEmitter.ListenerSubscription
- Direction
- packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.EventEmitter, so a change to packages.react-native-video.src.core.types.EventEmitter can break packages.react-native-video.src.core.types.VideoPlayerBase, while a change to packages.react-native-video.src.core.types.VideoPlayerBase can't break packages.react-native-video.src.core.types.EventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoPlayerBase uses a module listed above it, which is the healthy direction.
27→5 packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.IgnoreSilentSwitchMode✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoPlayerBase uses a type in packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.
- The types involved
packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase→packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.IgnoreSilentSwitchMode
- Direction
- packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.IgnoreSilentSwitchMode, so a change to packages.react-native-video.src.core.types.IgnoreSilentSwitchMode can break packages.react-native-video.src.core.types.VideoPlayerBase, while a change to packages.react-native-video.src.core.types.VideoPlayerBase can't break packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoPlayerBase uses a module listed above it, which is the healthy direction.
27→6 packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.MixAudioMode✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoPlayerBase uses a type in packages.react-native-video.src.core.types.MixAudioMode.
- The types involved
packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase→packages.react-native-video.src.core.types.MixAudioMode.MixAudioMode
- Direction
- packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.MixAudioMode, so a change to packages.react-native-video.src.core.types.MixAudioMode can break packages.react-native-video.src.core.types.VideoPlayerBase, while a change to packages.react-native-video.src.core.types.VideoPlayerBase can't break packages.react-native-video.src.core.types.MixAudioMode.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoPlayerBase uses a module listed above it, which is the healthy direction.
27→8 packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.VideoPlayerStatus✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoPlayerBase uses a type in packages.react-native-video.src.core.types.VideoPlayerStatus.
- The types involved
packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase→packages.react-native-video.src.core.types.VideoPlayerStatus.VideoPlayerStatus
- Direction
- packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.VideoPlayerStatus, so a change to packages.react-native-video.src.core.types.VideoPlayerStatus can break packages.react-native-video.src.core.types.VideoPlayerBase, while a change to packages.react-native-video.src.core.types.VideoPlayerBase can't break packages.react-native-video.src.core.types.VideoPlayerStatus.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoPlayerBase uses a module listed above it, which is the healthy direction.
27→24 packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.VideoPlayerSourceBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.types.VideoPlayerBase uses a type in packages.react-native-video.src.core.types.VideoPlayerSourceBase.
- The types involved
packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase→packages.react-native-video.src.core.types.VideoPlayerSourceBase.VideoPlayerSourceBase
- Direction
- packages.react-native-video.src.core.types.VideoPlayerBase uses packages.react-native-video.src.core.types.VideoPlayerSourceBase, so a change to packages.react-native-video.src.core.types.VideoPlayerSourceBase can break packages.react-native-video.src.core.types.VideoPlayerBase, while a change to packages.react-native-video.src.core.types.VideoPlayerBase can't break packages.react-native-video.src.core.types.VideoPlayerSourceBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.types.VideoPlayerBase uses a module listed above it, which is the healthy direction.
28→15 com.twg.video.core uses com.twg.video.view✕
- Connections
- 1 pair of types, where a type in com.twg.video.core uses a type in com.twg.video.view.
- The types involved
com.twg.video.core.VideoManager→com.twg.video.view.VideoView
- Direction
- com.twg.video.core uses com.twg.video.view, so a change to com.twg.video.view can break com.twg.video.core, while a change to com.twg.video.core can't break com.twg.video.view.
- Position
- Below the diagonal: com.twg.video.core uses a module listed above it, which is the healthy direction.
28→25 com.twg.video.core uses com.margelo.nitro.video✕
- Connections
- 2 pairs of types, where a type in com.twg.video.core uses a type in com.margelo.nitro.video.
- The types involved
com.twg.video.core.AudioFocusManager→com.margelo.nitro.video.HybridVideoPlayercom.twg.video.core.VideoManager→com.margelo.nitro.video.HybridVideoPlayer
- Direction
- com.twg.video.core uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.video.core, while a change to com.twg.video.core can't break com.margelo.nitro.video.
- Position
- Below the diagonal: com.twg.video.core uses a module listed above it, which is the healthy direction.
29→12 com.twg.video.core.plugins uses com.twg.video.core.player✕
- Connections
- 3 pairs of types, where a type in com.twg.video.core.plugins uses a type in com.twg.video.core.player.
- The types involved
com.twg.video.core.plugins.PluginsRegistry→com.twg.video.core.player.DRMManagerSpeccom.twg.video.core.plugins.ReactNativeVideoPlugin→com.twg.video.core.player.DRMManagerSpeccom.twg.video.core.plugins.ReactNativeVideoPluginSpec→com.twg.video.core.player.DRMManagerSpec
- Direction
- com.twg.video.core.plugins uses com.twg.video.core.player, so a change to com.twg.video.core.player can break com.twg.video.core.plugins, while a change to com.twg.video.core.plugins can't break com.twg.video.core.player.
- Position
- Below the diagonal: com.twg.video.core.plugins uses a module listed above it, which is the healthy direction.
29→15 com.twg.video.core.plugins uses com.twg.video.view✕
- Connections
- 3 pairs of types, where a type in com.twg.video.core.plugins uses a type in com.twg.video.view.
- The types involved
com.twg.video.core.plugins.PluginsRegistry→com.twg.video.view.VideoViewcom.twg.video.core.plugins.ReactNativeVideoPlugin→com.twg.video.view.VideoViewcom.twg.video.core.plugins.ReactNativeVideoPluginSpec→com.twg.video.view.VideoView
- Direction
- com.twg.video.core.plugins uses com.twg.video.view, so a change to com.twg.video.view can break com.twg.video.core.plugins, while a change to com.twg.video.core.plugins can't break com.twg.video.view.
- Position
- Below the diagonal: com.twg.video.core.plugins uses a module listed above it, which is the healthy direction.
29→25 com.twg.video.core.plugins uses com.margelo.nitro.video✕
- Connections
- 6 pairs of types, where a type in com.twg.video.core.plugins uses a type in com.margelo.nitro.video.
- The types involved
com.twg.video.core.plugins.PluginsRegistry→com.margelo.nitro.video.HybridVideoPlayercom.twg.video.core.plugins.PluginsRegistry→com.margelo.nitro.video.HybridVideoPlayerSourcecom.twg.video.core.plugins.ReactNativeVideoPlugin→com.margelo.nitro.video.HybridVideoPlayercom.twg.video.core.plugins.ReactNativeVideoPlugin→com.margelo.nitro.video.HybridVideoPlayerSourcecom.twg.video.core.plugins.ReactNativeVideoPluginSpec→com.margelo.nitro.video.HybridVideoPlayercom.twg.video.core.plugins.ReactNativeVideoPluginSpec→com.margelo.nitro.video.HybridVideoPlayerSource
- Direction
- com.twg.video.core.plugins uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.video.core.plugins, while a change to com.twg.video.core.plugins can't break com.margelo.nitro.video.
- Position
- Below the diagonal: com.twg.video.core.plugins uses a module listed above it, which is the healthy direction.
30→12 com.twg.videodrm.DRMManager uses com.twg.video.core.player✕
- Connections
- 1 pair of types, where a type in com.twg.videodrm.DRMManager uses a type in com.twg.video.core.player.
- The types involved
com.twg.videodrm.DRMManager.DRMManager→com.twg.video.core.player.DRMManagerSpec
- Direction
- com.twg.videodrm.DRMManager uses com.twg.video.core.player, so a change to com.twg.video.core.player can break com.twg.videodrm.DRMManager, while a change to com.twg.videodrm.DRMManager can't break com.twg.video.core.player.
- Position
- Below the diagonal: com.twg.videodrm.DRMManager uses a module listed above it, which is the healthy direction.
30→25 com.twg.videodrm.DRMManager uses com.margelo.nitro.video✕
- Connections
- 1 pair of types, where a type in com.twg.videodrm.DRMManager uses a type in com.margelo.nitro.video.
- The types involved
com.twg.videodrm.DRMManager.DRMManager→com.margelo.nitro.video.HybridVideoPlayerSource
- Direction
- com.twg.videodrm.DRMManager uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.videodrm.DRMManager, while a change to com.twg.videodrm.DRMManager can't break com.margelo.nitro.video.
- Position
- Below the diagonal: com.twg.videodrm.DRMManager uses a module listed above it, which is the healthy direction.
31→5 packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.IgnoreSilentSwitchMode✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer uses a type in packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.
- The types involved
packages.react-native-video.src.core.VideoPlayer.VideoPlayer→packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.IgnoreSilentSwitchMode
- Direction
- packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.IgnoreSilentSwitchMode, so a change to packages.react-native-video.src.core.types.IgnoreSilentSwitchMode can break packages.react-native-video.src.core.VideoPlayer, while a change to packages.react-native-video.src.core.VideoPlayer can't break packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer uses a module listed above it, which is the healthy direction.
31→6 packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.MixAudioMode✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer uses a type in packages.react-native-video.src.core.types.MixAudioMode.
- The types involved
packages.react-native-video.src.core.VideoPlayer.VideoPlayer→packages.react-native-video.src.core.types.MixAudioMode.MixAudioMode
- Direction
- packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.MixAudioMode, so a change to packages.react-native-video.src.core.types.MixAudioMode can break packages.react-native-video.src.core.VideoPlayer, while a change to packages.react-native-video.src.core.VideoPlayer can't break packages.react-native-video.src.core.types.MixAudioMode.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer uses a module listed above it, which is the healthy direction.
31→8 packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.VideoPlayerStatus✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer uses a type in packages.react-native-video.src.core.types.VideoPlayerStatus.
- The types involved
packages.react-native-video.src.core.VideoPlayer.VideoPlayer→packages.react-native-video.src.core.types.VideoPlayerStatus.VideoPlayerStatus
- Direction
- packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.VideoPlayerStatus, so a change to packages.react-native-video.src.core.types.VideoPlayerStatus can break packages.react-native-video.src.core.VideoPlayer, while a change to packages.react-native-video.src.core.VideoPlayer can't break packages.react-native-video.src.core.types.VideoPlayerStatus.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer uses a module listed above it, which is the healthy direction.
31→26 packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.Events✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer uses a type in packages.react-native-video.src.core.types.Events.
- The types involved
packages.react-native-video.src.core.VideoPlayer.VideoPlayer→packages.react-native-video.src.core.types.Events.VideoPlayerEvents
- Direction
- packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.Events, so a change to packages.react-native-video.src.core.types.Events can break packages.react-native-video.src.core.VideoPlayer, while a change to packages.react-native-video.src.core.VideoPlayer can't break packages.react-native-video.src.core.types.Events.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer uses a module listed above it, which is the healthy direction.
31→27 packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.VideoPlayerBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer uses a type in packages.react-native-video.src.core.types.VideoPlayerBase.
- The types involved
packages.react-native-video.src.core.VideoPlayer.VideoPlayer→packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase
- Direction
- packages.react-native-video.src.core.VideoPlayer uses packages.react-native-video.src.core.types.VideoPlayerBase, so a change to packages.react-native-video.src.core.types.VideoPlayerBase can break packages.react-native-video.src.core.VideoPlayer, while a change to packages.react-native-video.src.core.VideoPlayer can't break packages.react-native-video.src.core.types.VideoPlayerBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer uses a module listed above it, which is the healthy direction.
32→5 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.IgnoreSilentSwitchMode✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.IgnoreSilentSwitchMode
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.IgnoreSilentSwitchMode, so a change to packages.react-native-video.src.core.types.IgnoreSilentSwitchMode can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.types.IgnoreSilentSwitchMode.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→6 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.MixAudioMode✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.types.MixAudioMode.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.types.MixAudioMode.MixAudioMode
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.MixAudioMode, so a change to packages.react-native-video.src.core.types.MixAudioMode can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.types.MixAudioMode.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→8 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.VideoPlayerStatus✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.types.VideoPlayerStatus.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.types.VideoPlayerStatus.VideoPlayerStatus
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.VideoPlayerStatus, so a change to packages.react-native-video.src.core.types.VideoPlayerStatus can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.types.VideoPlayerStatus.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→9 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.WebVideoPlayer✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.types.WebVideoPlayer.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.types.WebVideoPlayer.WebVideoPlayer
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.WebVideoPlayer, so a change to packages.react-native-video.src.core.types.WebVideoPlayer can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.types.WebVideoPlayer.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→10 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.web.WebMediaProxy✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.web.WebMediaProxy.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.web.WebMediaProxy.WebMediaProxy
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.web.WebMediaProxy, so a change to packages.react-native-video.src.core.web.WebMediaProxy can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.web.WebMediaProxy.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→18 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.web.WebEventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.web.WebEventEmitter.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.web.WebEventEmitter.WebEventEmitter
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.web.WebEventEmitter, so a change to packages.react-native-video.src.core.web.WebEventEmitter can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.web.WebEventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→24 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.VideoPlayerSourceBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.types.VideoPlayerSourceBase.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.types.VideoPlayerSourceBase.VideoPlayerSourceBase
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.VideoPlayerSourceBase, so a change to packages.react-native-video.src.core.types.VideoPlayerSourceBase can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.types.VideoPlayerSourceBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
32→26 packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.Events✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.VideoPlayer_web uses a type in packages.react-native-video.src.core.types.Events.
- The types involved
packages.react-native-video.src.core.VideoPlayer_web.VideoPlayer→packages.react-native-video.src.core.types.Events.VideoPlayerEvents
- Direction
- packages.react-native-video.src.core.VideoPlayer_web uses packages.react-native-video.src.core.types.Events, so a change to packages.react-native-video.src.core.types.Events can break packages.react-native-video.src.core.VideoPlayer_web, while a change to packages.react-native-video.src.core.VideoPlayer_web can't break packages.react-native-video.src.core.types.Events.
- Position
- Below the diagonal: packages.react-native-video.src.core.VideoPlayer_web uses a module listed above it, which is the healthy direction.
33→27 packages.react-native-video.src.core.video-view.VideoViewProps uses packages.react-native-video.src.core.types.VideoPlayerBase✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.video-view.VideoViewProps uses a type in packages.react-native-video.src.core.types.VideoPlayerBase.
- The types involved
packages.react-native-video.src.core.video-view.VideoViewProps.VideoViewProps→packages.react-native-video.src.core.types.VideoPlayerBase.VideoPlayerBase
- Direction
- packages.react-native-video.src.core.video-view.VideoViewProps uses packages.react-native-video.src.core.types.VideoPlayerBase, so a change to packages.react-native-video.src.core.types.VideoPlayerBase can break packages.react-native-video.src.core.video-view.VideoViewProps, while a change to packages.react-native-video.src.core.video-view.VideoViewProps can't break packages.react-native-video.src.core.types.VideoPlayerBase.
- Position
- Below the diagonal: packages.react-native-video.src.core.video-view.VideoViewProps uses a module listed above it, which is the healthy direction.
34→28 com.twg.video.core.LibraryError uses com.twg.video.core✕
- Connections
- 4 pairs of types, where a type in com.twg.video.core.LibraryError uses a type in com.twg.video.core.
- The types involved
com.twg.video.core.LibraryError.ApplicationContextNotFound→com.twg.video.core.LibraryErrorcom.twg.video.core.LibraryError.DRMPluginNotFound→com.twg.video.core.LibraryErrorcom.twg.video.core.LibraryError.Deallocated→com.twg.video.core.LibraryErrorcom.twg.video.core.LibraryError.MethodNotSupported→com.twg.video.core.LibraryError
- Direction
- com.twg.video.core.LibraryError uses com.twg.video.core, so a change to com.twg.video.core can break com.twg.video.core.LibraryError, while a change to com.twg.video.core.LibraryError can't break com.twg.video.core.
- Position
- Below the diagonal: com.twg.video.core.LibraryError uses a module listed above it, which is the healthy direction.
35→28 com.twg.video.core.PlayerError uses com.twg.video.core✕
- Connections
- 5 pairs of types, where a type in com.twg.video.core.PlayerError uses a type in com.twg.video.core.
- The types involved
com.twg.video.core.PlayerError.AssetNotInitialized→com.twg.video.core.PlayerErrorcom.twg.video.core.PlayerError.Cancelled→com.twg.video.core.PlayerErrorcom.twg.video.core.PlayerError.InvalidSource→com.twg.video.core.PlayerErrorcom.twg.video.core.PlayerError.NotInitialized→com.twg.video.core.PlayerErrorcom.twg.video.core.PlayerError.PlaybackFailed→com.twg.video.core.PlayerError
- Direction
- com.twg.video.core.PlayerError uses com.twg.video.core, so a change to com.twg.video.core can break com.twg.video.core.PlayerError, while a change to com.twg.video.core.PlayerError can't break com.twg.video.core.
- Position
- Below the diagonal: com.twg.video.core.PlayerError uses a module listed above it, which is the healthy direction.
36→28 com.twg.video.core.SourceError uses com.twg.video.core✕
- Connections
- 6 pairs of types, where a type in com.twg.video.core.SourceError uses a type in com.twg.video.core.
- The types involved
com.twg.video.core.SourceError.Cancelled→com.twg.video.core.SourceErrorcom.twg.video.core.SourceError.FailedToInitializeAsset→com.twg.video.core.SourceErrorcom.twg.video.core.SourceError.FileDoesNotExist→com.twg.video.core.SourceErrorcom.twg.video.core.SourceError.InvalidUri→com.twg.video.core.SourceErrorcom.twg.video.core.SourceError.MissingReadFilePermission→com.twg.video.core.SourceErrorcom.twg.video.core.SourceError.UnsupportedContentType→com.twg.video.core.SourceError
- Direction
- com.twg.video.core.SourceError uses com.twg.video.core, so a change to com.twg.video.core can break com.twg.video.core.SourceError, while a change to com.twg.video.core.SourceError can't break com.twg.video.core.
- Position
- Below the diagonal: com.twg.video.core.SourceError uses a module listed above it, which is the healthy direction.
37→28 com.twg.video.core.VideoViewError uses com.twg.video.core✕
- Connections
- 3 pairs of types, where a type in com.twg.video.core.VideoViewError uses a type in com.twg.video.core.
- The types involved
com.twg.video.core.VideoViewError.PictureInPictureNotSupported→com.twg.video.core.VideoViewErrorcom.twg.video.core.VideoViewError.ViewIsDeallocated→com.twg.video.core.VideoViewErrorcom.twg.video.core.VideoViewError.ViewNotFound→com.twg.video.core.VideoViewError
- Direction
- com.twg.video.core.VideoViewError uses com.twg.video.core, so a change to com.twg.video.core can break com.twg.video.core.VideoViewError, while a change to com.twg.video.core.VideoViewError can't break com.twg.video.core.
- Position
- Below the diagonal: com.twg.video.core.VideoViewError uses a module listed above it, which is the healthy direction.
38→12 com.twg.videodrm uses com.twg.video.core.player✕
- Connections
- 1 pair of types, where a type in com.twg.videodrm uses a type in com.twg.video.core.player.
- The types involved
com.twg.videodrm.DRMPlugin→com.twg.video.core.player.DRMManagerSpec
- Direction
- com.twg.videodrm uses com.twg.video.core.player, so a change to com.twg.video.core.player can break com.twg.videodrm, while a change to com.twg.videodrm can't break com.twg.video.core.player.
- Position
- Below the diagonal: com.twg.videodrm uses a module listed above it, which is the healthy direction.
38→25 com.twg.videodrm uses com.margelo.nitro.video✕
- Connections
- 1 pair of types, where a type in com.twg.videodrm uses a type in com.margelo.nitro.video.
- The types involved
com.twg.videodrm.DRMPlugin→com.margelo.nitro.video.HybridVideoPlayerSource
- Direction
- com.twg.videodrm uses com.margelo.nitro.video, so a change to com.margelo.nitro.video can break com.twg.videodrm, while a change to com.twg.videodrm can't break com.margelo.nitro.video.
- Position
- Below the diagonal: com.twg.videodrm uses a module listed above it, which is the healthy direction.
38→29 com.twg.videodrm uses com.twg.video.core.plugins✕
- Connections
- 1 pair of types, where a type in com.twg.videodrm uses a type in com.twg.video.core.plugins.
- The types involved
com.twg.videodrm.DRMPlugin→com.twg.video.core.plugins.ReactNativeVideoPlugin
- Direction
- com.twg.videodrm uses com.twg.video.core.plugins, so a change to com.twg.video.core.plugins can break com.twg.videodrm, while a change to com.twg.videodrm can't break com.twg.video.core.plugins.
- Position
- Below the diagonal: com.twg.videodrm uses a module listed above it, which is the healthy direction.
39→4 packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.types.EventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.video-view uses a type in packages.react-native-video.src.core.types.EventEmitter.
- The types involved
packages.react-native-video.src.core.video-view.useViewEvents.web→packages.react-native-video.src.core.types.EventEmitter.ListenerSubscription
- Direction
- packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.types.EventEmitter, so a change to packages.react-native-video.src.core.types.EventEmitter can break packages.react-native-video.src.core.video-view, while a change to packages.react-native-video.src.core.video-view can't break packages.react-native-video.src.core.types.EventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.video-view uses a module listed above it, which is the healthy direction.
39→18 packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.web.WebEventEmitter✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.video-view uses a type in packages.react-native-video.src.core.web.WebEventEmitter.
- The types involved
packages.react-native-video.src.core.video-view.useViewEvents.web→packages.react-native-video.src.core.web.WebEventEmitter.WebEventEmitter
- Direction
- packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.web.WebEventEmitter, so a change to packages.react-native-video.src.core.web.WebEventEmitter can break packages.react-native-video.src.core.video-view, while a change to packages.react-native-video.src.core.video-view can't break packages.react-native-video.src.core.web.WebEventEmitter.
- Position
- Below the diagonal: packages.react-native-video.src.core.video-view uses a module listed above it, which is the healthy direction.
39→26 packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.types.Events✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.video-view uses a type in packages.react-native-video.src.core.types.Events.
- The types involved
packages.react-native-video.src.core.video-view.useViewEvents.web→packages.react-native-video.src.core.types.Events.VideoViewEvents
- Direction
- packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.types.Events, so a change to packages.react-native-video.src.core.types.Events can break packages.react-native-video.src.core.video-view, while a change to packages.react-native-video.src.core.video-view can't break packages.react-native-video.src.core.types.Events.
- Position
- Below the diagonal: packages.react-native-video.src.core.video-view uses a module listed above it, which is the healthy direction.
39→33 packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.video-view.VideoViewProps✕
- Connections
- 1 pair of types, where a type in packages.react-native-video.src.core.video-view uses a type in packages.react-native-video.src.core.video-view.VideoViewProps.
- The types involved
packages.react-native-video.src.core.video-view.VideoView→packages.react-native-video.src.core.video-view.VideoViewProps.VideoViewProps
- Direction
- packages.react-native-video.src.core.video-view uses packages.react-native-video.src.core.video-view.VideoViewProps, so a change to packages.react-native-video.src.core.video-view.VideoViewProps can break packages.react-native-video.src.core.video-view, while a change to packages.react-native-video.src.core.video-view can't break packages.react-native-video.src.core.video-view.VideoViewProps.
- Position
- Below the diagonal: packages.react-native-video.src.core.video-view uses a module listed above it, which is the healthy direction.
40→38 com.margelo.nitro.videodrm uses com.twg.videodrm✕
- Connections
- 1 pair of types, where a type in com.margelo.nitro.videodrm uses a type in com.twg.videodrm.
- The types involved
com.margelo.nitro.videodrm.PluginManager→com.twg.videodrm.DRMPlugin
- Direction
- com.margelo.nitro.videodrm uses com.twg.videodrm, so a change to com.twg.videodrm can break com.margelo.nitro.videodrm, while a change to com.margelo.nitro.videodrm can't break com.twg.videodrm.
- Position
- Below the diagonal: com.margelo.nitro.videodrm uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 98 | High / Critical |
| A05:2025 — Injection | 45 | High / Critical |
Roadmap
Top priorities: Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run. | +7.1 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +3.6 pts | Medium | Security & performance tooling |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +3.1 pts | Medium | Dependency Hygiene |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.1 pts | Medium | Release Hygiene |
| Resolve the 55 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (55). | +1.6 pts | Medium | Dependency Vulnerabilities |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 27 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). | +0.7 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| packages/react-native-video/ios/core/VideoManager.swift | 6.0 | Mixed | Explicit Debt: TodoComment |
| packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift | 7.0 | Mixed | God Classes: TooManyMethods: HybridVideoPlayerEventEmitter |
| packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift | 7.0 | Mixed | Cyclomatic Complexity: HybridVideoPlayer.initializePlayerItem (cyclomatic 17) |
| packages/react-native-video/ios/core/HLSSubtitleInjector.swift | 7.1 | Mixed | Cyclomatic Complexity: HLSSubtitleInjector.modifyM3U8Content (cyclomatic 22) |
| packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt | 7.2 | Mixed | Cognitive Complexity: TextTrackUtils.selectTextTrack (cognitive 26) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 59 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 59 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 289 of 317 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `docs/docusaurus.config.ts`, `packages/react-native-video/ios/core/HLSSubtitleInjector.swift`, `packages/react-native-video/ios/core/Utils/HLSManifestParser.swift`, `packages/react-native-video/src/core/hooks/useManagedInstance.ts`, `packages/react-native-video/src/index.tsx` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/react-native-video/ios/core/HLSSubtitleInjector.swift, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): REDACTED has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift, c, cpp, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Kotlin, Swift, c, cpp, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was HLSSubtitleInjector.modifyM3U8Content at 22. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being VideoPlayerEvents.addEventListener at 23 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/react-native-video/src/core/events/VideoPlayerEvents.native.ts (VideoPlayerEvents.addEventListener at 23). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with HLSSubtitleInjector.modifyM3U8Content (cyclomatic 22), VideoView.VideoView (cyclomatic 21), HybridVideoPlayer.initializePlayerItem (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
18 method(s) exceeded the cognitive complexity threshold of 15; the worst was HLSSubtitleInjector.modifyM3U8Content at 37.
What to do
- Bring the 18 bodies over 15 down to 15 or less in Cognitive Complexity — start with HLSSubtitleInjector.modifyM3U8Content (cognitive 37), PictureInPictureHelperFragment.onPictureInPictureModeChanged (cognitive 37), HybridVideoPlayer.initializePlayerItem (cognitive 27). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 18 together lifts Cognitive Complexity from 7.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
5 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with HybridVideoPlayerEventEmitter.kt, HybridVideoPlayerEventEmitter.swift, HybridVideoPlayer.swift. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with V7ProPlugins.tsx. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with HybridVideoPlayer.swift. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. A further 16 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. Measured on part of this repository only: .ts, .tsx (38% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 7 Edited copy of a member (3 corresponding lines) finding(s) in Code Duplication — start with HybridVideoPlayerEventEmitter.swift (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 Edited copy of a member (40 corresponding lines) finding(s) in Code Duplication — start with HybridVideoPlayer.swift, TextTrackUtils.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with VideoView.kt, PictureInPictureUtils.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
4 production modules (Gradle+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 3 of the 4 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 16 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with VideoComponentView.swift, HybridVideoViewViewManager.swift, DRMManager.swift. — One of this dimension's main actionable groups (3 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D10 · Test Quality
1 skipped (1 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 236 tests.
D12 · Dependency Hygiene
2 outdated direct gem(s), 0 pinning defect(s). 8 declaration(s) graded against rubygems.org, 3 of them against a version resolved in a committed Gemfile.lock. 3 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 5 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed Gemfile.lock. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares REDACTED, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift (3×17=51) Repeated repair below the complexity floor: packages/react-native-video/android/src/main/java/com/twg/video/hybrids/videoplayer/HybridVideoPlayer.kt (5 of 6 changes were fixes); packages/react-native-video/src/core/types/VideoError.ts (3 of 3 changes were fixes)
What to do
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with HybridVideoPlayer.kt, VideoError.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with HybridVideoPlayer.swift. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/react-native-video/ios/core/NowPlayingInfoCenterManager.swift. Counted over 63 of the 147 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
5 deducted task-comment markers across 15914 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 5 TodoComment finding(s) in Explicit Debt — start with VideoManager.swift, VideoPlayerObserver.swift, CustomMediaNotificationProvider.kt. — One of this dimension's main actionable groups (5 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 60 document(s) read across 5 unit(s).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D24 · Comment Value
4 of 167 judged comments only repeat the code they sit on (2.4 %). 8 comment(s) in another language or script were not judged.
What to do
- Resolve the 4 redundant comment finding(s) in Comment Value — start with VideoPlayer.ts (4). — One of this dimension's main actionable groups (4 recommendation-level).
D26 · Project Cohesion
1 of 5 build units (Gradle, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
45 finding(s): 0 critical, 34 high, 11 medium, 0 low. 27 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 11 file(s) — `docs/docusaurus.config.ts` (line 63, line 184), `e2e/fixtures/media/hls/seg_000.ts` (line 1), `e2e/fixtures/media/hls/seg_001.ts` (line 1), `e2e/fixtures/media/hls/seg_002.ts` (line 1), `e2e/fixtures/media/hls/seg_003.ts` (line 1), … (+6 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 6 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 27 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (28 issue-level, 1 of them charged here).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
93 finding(s): 9 critical, 57 high, 24 medium, 3 low.
What to do
- Resolve the 55 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (55). — One of this dimension's main actionable groups (55 issue-level).
- Resolve the 9 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D34 · Knowledge Freshness
31 of 63 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/react-native-video/ios/core/HLSSubtitleInjector.swift. Counted over 63 of the 147 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with HLSSubtitleInjector.swift, VideoPlayer.web.ts, FullscreenVideoFragment.kt. — One of this dimension's main actionable groups (31 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 12 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- 1 ADR-shaped document(s) detected by content — `e2e/CONTEXT.md`. They are not under a conventional ADR folder (docs/adr/) and are not named NNNN-title.md, and this check found them by their decision signature rather than by where they live — so a reader who does not already know these paths has no route to them. Detected by content signature only: records kept outside the repository, or written without a Status/Decision/Consequences shape, are not visible to this check and are not counted here.
What to do
- Move ADRs under docs/adr/ (or docs/adrs/) and name them NNNN-title.md so they're easy to find.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 175 JavaScript/TypeScript, Swift, JVM production file(s) this check read across 7 module(s). Each was searched for its ecosystem's logging libraries (JVM: SLF4J, Log4j2, java.util.logging, Logback, kotlin-logging, scala-logging; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; Swift: os.Logger/os_log/NSLog, swift-log, CocoaLumberjack, SwiftyBeaver, XCGLogger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt SLF4J (with a Logback or Log4j2 JSON encoder) and log at meaningful points in the modules you run.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 13 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/cache-cleanup.yml:21
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `bun`, `gradle`, `bundler`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:4
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `bun`, `gradle`, `bundler` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- packages/react-native-video/src/core/VideoPlayer.ts:220 · packages/react-native-video/src/core/VideoPlayer.ts:253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/react-native-video/src/core/VideoPlayer.ts:220
- packages/react-native-video/src/expo-plugins/writeToPodfile.ts:36 · packages/react-native-video/src/expo-plugins/writeToPodfile.ts:62 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/react-native-video/src/expo-plugins/writeToPodfile.ts:36
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- packages/react-native-video/src/core/video-view/NativeVideoView.tsx:3 imports packages/react-native-video/src/spec/fabric/VideoViewNativeComponent.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/react-native-video/src/core/video-view/NativeVideoView.tsx:3
- packages/react-native-video/src/expo-plugins/writeToPodfile.ts:1 imports @expo/config-plugins/build/utils/generateCode, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/react-native-video/src/expo-plugins/writeToPodfile.ts:1
What to do
- Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (1 row); move the shared test helper into a source directory production code may depend on (1 row).
R2 · Cyclomatic Complexity
- apply has cyclomatic complexity 49 and cognitive complexity 69; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — test-app/src/e2e/eventLog.ts:170
- (anonymous) has cyclomatic complexity 13 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/react-native-video/src/core/utils/sourceFactory.ts:117
- main has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/e2e/nightly-issue.mjs:53
R3 · Large Files
R4 · Test Coverage
- scripts/e2e/matrix-plan.test.mjs:23 imports '../../e2e/flows', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — scripts/e2e/matrix-plan.test.mjs:23
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×10) — packages/react-native-video/src/core/VideoPlayer.web.ts:1, packages/react-native-video/src/core/web/webDOMEvents.ts:1, packages/react-native-video/src/core/video-view/VideoView.web.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- This repository declares test tooling, and the ✓ above records that declaration — but scripts/e2e/matrix-plan.test.mjs cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — scripts/e2e/matrix-plan.test.mjs:23
R7 · Dead Code
- Unreachable from the 8 application, 16 tooling and 47 test entry point(s) detected in this repo. Gate removals on `bun run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/react-native-video/src/core/video-view/VideoView.web.tsx, packages/react-native-video/src/core/video-view/useViewEvents.web.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/VideoPlayer.web.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/react-native-video/src/core/web/WebEventEmitter.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/web/webDOMEvents.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — packages/react-native-video/src/core/video-view/VideoView.web.tsx, packages/react-native-video/src/core/events/VideoPlayerEvents.web.ts, packages/react-native-video/src/core/utils/playerFactory.web.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/react-native-video/src/core/VideoPlayer.web.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/web/MediaSession.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/react-native-video/src/core/VideoPlayer.web.ts, packages/react-native-video/src/core/web/WebEventEmitter.ts, packages/react-native-video/src/core/web/webDOMEvents.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/web/WebMediaProxy.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/react-native-video/src/core/video-view/VideoView.web.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/video-view/useViewEvents.web.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/react-native-video/src/core/VideoPlayer.web.ts, packages/react-native-video/src/core/events/VideoPlayerEvents.web.ts, packages/react-native-video/src/core/video-view/useViewEvents.web.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/web/WebEventEmitter.ts
- no import path from any entry point (8 application, 16 tooling, 47 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/react-native-video/src/core/VideoPlayer.web.ts, packages/react-native-video/src/core/video-view/VideoView.web.tsx, packages/react-native-video/src/core/web/MediaSession.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/react-native-video/src/core/web/VideoStore.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. — packages/react-native-video/react-native.config.js:7
- Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×7)
- Declared in test-app/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×10) — packages/react-native-video/src/expo-plugins/getPackageInfo.ts:10, packages/react-native-video/src/expo-plugins/getPackageInfo.ts:20, packages/react-native-video/src/core/web/MediaSession.ts:77, …
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — packages/react-native-video/src/core/VideoPlayer.web.ts:281
- `catch (_: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×5) — packages/react-native-video/android/src/main/java/com/twg/video/core/VideoManager.kt:262, packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackService.kt:192, packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackServiceConnection.kt:120, …
- `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — packages/react-native-video/android/src/main/java/com/twg/video/core/utils/VideoFileHelper.kt:47, packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/CustomMediaNotificationProvider.kt:94
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 2/8 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~1.7 `!` null assertions per 1k TypeScript source lines — 10 assertion(s) across the 5739 source line(s) of the 82 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/react-native-video/src/core/VideoPlayer.web.ts (6), packages/react-native-video/src/core/web/webDOMEvents.ts (2), packages/react-native-video/src/core/web/WebEventEmitter.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 63% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 87% | Strong | Solid. |
| Maturity | 70% | Strong | Solid. |
| Readiness | 43% | Weak — gated by R8, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 60% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — AX6 reached only 40% of this repository's production lines — swift (4,939 lines), kotlin (4,673 lines), objectivec (130 lines), c (14 lines), cpp (10 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): REDACTED has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with REDACTED is what lets the suite be re-run.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 3 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .cpp, .kt, .m, .mm, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 5 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (npm error code ERESOLVE), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 22 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Swift source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 29% of this repository's production lines — typescript (6,302 lines), swift (4,939 lines), javascript (182 lines), objectivec (130 lines), c (14 lines), cpp (10 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Kotlin was read, and it logs through none that an assembled message defeats: Android's `Log` and Timber, java.util.logging and log4j-api-kotlin take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J, log4j 2 or kotlin-logging (`LoggerFactory.getLogger`, `KotlinLogging.logger {}`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 102 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite cannot be installed from its own lockfile: the repository root
- Test suite cannot be installed from its own lockfile: packages/react-native-video/
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 159 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (empty catch) packages/react-native-video/src/expo-plugins/getPackageInfo.ts:10
- Swallowed exception (empty catch) packages/react-native-video/src/expo-plugins/getPackageInfo.ts:20
- Swallowed exception (empty catch) packages/react-native-video/src/core/VideoPlayer.web.ts:281
- Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts:77
- Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts:96
- Swallowed exception (empty catch) packages/react-native-video/src/core/web/MediaSession.ts:109
- Swallowed exception (empty catch) packages/react-native-video/src/core/video-view/VideoView.web.tsx:52
- Swallowed exception (empty catch) packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackService.kt:152
- Swallowed exception (empty catch) packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackServiceConnection.kt:134
- Swallowed exception (empty catch) packages/react-native-video/android/src/main/java/com/twg/video/core/fragments/FullscreenVideoFragment.kt:82
- Swallowed exception (empty catch) packages/drm-plugin/android/src/main/java/com/twg/videodrm/PluginManager.kt:50
- No test reaches this file packages/react-native-video/src/core/VideoPlayer.web.ts:1
- No test reaches this file packages/react-native-video/src/core/web/webDOMEvents.ts:1
- No test reaches this file packages/react-native-video/src/core/video-view/VideoView.web.tsx:1
- No test reaches this file packages/react-native-video/src/core/web/MediaSession.ts:1
- No test reaches this file packages/react-native-video/src/core/web/WebMediaProxy.ts:1
- No test reaches this file packages/react-native-video/src/core/video-view/useViewEvents.web.ts:1
- No test reaches this file packages/react-native-video/src/core/web/WebEventEmitter.ts:1
- No test reaches this file packages/react-native-video/src/core/events/VideoPlayerEvents.web.ts:1
- No test reaches this file packages/drm-plugin/src/index.tsx:1
- No test reaches this file packages/react-native-video/src/core/utils/playerFactory.web.ts:1
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:136
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:144
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:50
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:58
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:132
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:152
- Edited copy of a member (3 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:184
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/VideoManager.kt:262
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/VideoFileHelper.kt:47
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/CustomMediaNotificationProvider.kt:94
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackService.kt:192
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackServiceConnection.kt:120
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/extensions/VideoPlaybackService+ServiceManagment.kt:21
- Swallowed exception (caught, then discarded) packages/react-native-video/android/src/main/java/com/twg/video/core/extensions/VideoPlaybackService+ServiceManagment.kt:32
- TodoComment packages/react-native-video/ios/core/VideoManager.swift:258
- TodoComment packages/react-native-video/ios/core/VideoPlayerObserver.swift:131
- TodoComment packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/CustomMediaNotificationProvider.kt:71
- TodoComment packages/react-native-video/android/src/main/java/com/twg/video/core/player/OnAudioFocusChangedListener.kt:6
- TodoComment packages/drm-plugin/ios/DRMManager/DRMManager+AVContentKeySessionDelegate.swift:58
- TooManyMethods: HybridVideoPlayerEventEmitter packages/react-native-video/android/src/main/java/com/twg/video/hybrids/videoplayereventemitter/HybridVideoPlayerEventEmitter.kt:9
- TooManyMethods: HybridVideoPlayerEventEmitter packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:17
- TooManyMethods: HybridVideoPlayer packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:12
- Low cohesion: VideoComponentView (LCOM4 8) packages/react-native-video/ios/view/VideoComponentView.swift:13
- Low cohesion: HybridVideoViewViewManager (LCOM4 6) packages/react-native-video/ios/hybrids/VideoViewViewManager/HybridVideoViewViewManager.swift:18
- Low cohesion: DRMManager (LCOM4 4) packages/drm-plugin/ios/DRMManager/DRMManager.swift:13
- Repeated repair: packages/react-native-video/android/src/main/java/com/twg/video/hybrids/videoplayer/HybridVideoPlayer.kt packages/react-native-video/android/src/main/java/com/twg/video/hybrids/videoplayer/HybridVideoPlayer.kt:219
- Repeated repair: packages/react-native-video/src/core/types/VideoError.ts packages/react-native-video/src/core/types/VideoError.ts:131
- Edited copy of a member (40 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:402
- Edited copy of a member (40 corresponding lines) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt:12
- Edited copy of a member (13 corresponding lines) packages/react-native-video/android/src/main/java/com/twg/video/view/VideoView.kt:291
- Edited copy of a member (13 corresponding lines) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/PictureInPictureUtils.kt:120
- Boundary violation [package:test-suite-dependency] packages/react-native-video/src/core/video-view/NativeVideoView.tsx:3
- Boundary violation [package:third-party-deep-import] packages/react-native-video/src/expo-plugins/writeToPodfile.ts:1
- HLSSubtitleInjector.modifyM3U8Content (cyclomatic 22) packages/react-native-video/ios/core/HLSSubtitleInjector.swift:56
- VideoView.VideoView (cyclomatic 21) packages/react-native-video/src/core/video-view/VideoView.tsx:61
- HybridVideoPlayer.initializePlayerItem (cyclomatic 17) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:542
- SmallVideoPlayerOptimizer.optimizeButtons (cyclomatic 17) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/SmallVideoPlayerOptimizer.kt:88
- AVAsset.estimatedMemoryUsage (cyclomatic 16) packages/react-native-video/ios/core/Extensions/AVAsset+estimatedMemoryUsage.swift:12
- Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile
- Hotspot: packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:542
- HLSSubtitleInjector.modifyM3U8Content (cognitive 37) packages/react-native-video/ios/core/HLSSubtitleInjector.swift:56
- PictureInPictureHelperFragment.onPictureInPictureModeChanged (cognitive 37) packages/react-native-video/android/src/main/java/com/twg/video/core/fragments/PictureInPictureHelperFragment.kt:41
- HybridVideoPlayer.initializePlayerItem (cognitive 27) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:542
- TextTrackUtils.selectTextTrack (cognitive 26) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt:53
- HLSSubtitleInjector.handleMainManifest (cognitive 23) packages/react-native-video/ios/core/HLSSubtitleInjector.swift:228
- AVAsset.estimatedMemoryUsage (cognitive 23) packages/react-native-video/ios/core/Extensions/AVAsset+estimatedMemoryUsage.swift:12
- webDOMEvents.attachTrackListeners (cognitive 22) packages/react-native-video/src/core/web/webDOMEvents.ts:141
- VideoManager.determineAudioCategory (cognitive 20) packages/react-native-video/ios/core/VideoManager.swift:295
- HybridVideoPlayer.selectTextTrack (cognitive 20) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:677
- AVAsset.getAssetInformation (cognitive 20) packages/react-native-video/ios/core/Extensions/AVAsset+getAssetInformation.swift:4
- HybridVideoPlayerSource.prepareAsset (cognitive 19) packages/react-native-video/ios/hybrids/VideoPlayerSource/HybridVideoPlayerSource.swift:207
- TextTrackUtils.getSelectedTrack (cognitive 18) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt:135
- VideoOrientationUtils.fromWHR (cognitive 18) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/VideoOrientationUtils.kt:6
- VideoView.VideoView (cognitive 18) packages/react-native-video/src/core/video-view/VideoView.tsx:61
- HLSSubtitleInjector.handleSubtitleM3U8 (cognitive 17) packages/react-native-video/ios/core/HLSSubtitleInjector.swift:279
- HybridVideoPlayerSource.getAssetInformationAsync (cognitive 16) packages/react-native-video/ios/hybrids/VideoPlayerSource/HybridVideoPlayerSource.swift:80
- SmallVideoPlayerOptimizer.isSmallVideoPlayer (cognitive 16) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/SmallVideoPlayerOptimizer.kt:12
- sourceFactory.createSource (cognitive 16) packages/react-native-video/src/core/utils/sourceFactory.ts:115
- FunctionTooLong: V7ProPlugins.V7ProPlugins docs/src/components/Intro/V7ProPlugins/V7ProPlugins.tsx:5
- ClassTooLong: HybridVideoPlayer packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:12
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (23 corresponding lines) packages/react-native-video/ios/view/VideoComponentViewObserver.swift:129
- Edited copy of a member (12 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerSource/SourceLoader.swift:89
- Edited copy of a member (7 corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:22
- Edited copy of a member (14 corresponding lines) packages/react-native-video/ios/core/VideoManager.swift:466
- Edited copies of one member (3 members, 9+ corresponding lines) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:42
- Duplicated block (24 lines × 2) packages/react-native-video/ios/hybrids/VideoPlayer/HybridVideoPlayer.swift:415
- Duplicated block (13 lines × 2) packages/react-native-video/ios/hybrids/VideoPlayerEmitter/HybridVideoPlayerEventEmitter.swift:30
- Duplicated block (11–12 lines × 2) packages/react-native-video/ios/core/HLSSubtitleInjector.swift:237
- Duplicated block (8 lines × 2) packages/react-native-video/ios/view/VideoComponentViewObserver.swift:135
- Duplicated block (9 lines × 2) packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt:16
- Off the main sequence: react-native-video
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplicated block (21 lines × 2 locations) packages/react-native-video/src/core/VideoPlayer.ts:220
- Duplicated block (16 lines × 2 locations) packages/react-native-video/src/expo-plugins/writeToPodfile.ts:36
- Complex function apply (cyclomatic 49, cognitive 69) test-app/src/e2e/eventLog.ts:170
- Complex function (anonymous) (cyclomatic 13, cognitive 17) packages/react-native-video/src/core/utils/sourceFactory.ts:117
- Complex function main (cyclomatic 11, cognitive 10) scripts/e2e/nightly-issue.mjs:53
- This test file cannot be loaded scripts/e2e/matrix-plan.test.mjs:23
- The declared test suite includes a file that cannot be loaded scripts/e2e/matrix-plan.test.mjs:23
- Dead file (~370 LoC) packages/react-native-video/src/core/VideoPlayer.web.ts
- Dead file (~215 LoC) packages/react-native-video/src/core/web/webDOMEvents.ts
- Dead file (~170 LoC) packages/react-native-video/src/core/video-view/VideoView.web.tsx
- Dead file (~131 LoC) packages/react-native-video/src/core/web/MediaSession.ts
- Dead file (~84 LoC) packages/react-native-video/src/core/web/WebMediaProxy.ts
- Dead file (~83 LoC) packages/react-native-video/src/core/video-view/useViewEvents.web.ts
- Dead file (~75 LoC) packages/react-native-video/src/core/web/WebEventEmitter.ts
- Dead file (~66 LoC) packages/react-native-video/src/core/web/VideoStore.ts
- Dead file (~23 LoC) packages/react-native-video/src/core/events/VideoPlayerEvents.web.ts
- Dead file (~6 LoC) packages/react-native-video/src/core/utils/playerFactory.web.ts
- Unlisted import '@react-native-community/cli-types' packages/react-native-video/react-native.config.js:7
- Unused dependency '@commitlint/config-conventional'
- Unused dependency '@eslint/js'
- Unused dependency '@evilmartians/lefthook'
- Unused dependency '@octokit/rest'
- Unused dependency '@release-it/bumper'
- Unused dependency '@release-it/conventional-changelog'
- Unused dependency 'conventional-changelog-conventionalcommits'
- Unused dependency '@react-native-community/cli-platform-android'
- Unused dependency '@react-native-community/cli-platform-ios'
Minor — 52 finding(s)
- Orphaned file packages/react-native-video/ios/core/HLSSubtitleInjector.swift:1
- Orphaned file packages/react-native-video/src/core/VideoPlayer.web.ts:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/fragments/FullscreenVideoFragment.kt:1
- Orphaned file packages/react-native-video/ios/view/VideoComponentView.swift:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/utils/TextTrackUtils.kt:1
- Orphaned file packages/react-native-video/src/core/types/Events.ts:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/plugins/PluginsRegistry.kt:1
- Orphaned file packages/react-native-video/ios/hybrids/VideoViewViewManager/HybridVideoViewViewManager.swift:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/hybrids/videoplayereventemitter/HybridVideoPlayerEventEmitter.kt:1
- Orphaned file packages/drm-plugin/ios/DRMManager/DRMManager.swift:1
- Orphaned file packages/react-native-video/src/core/types/VideoPlayerBase.ts:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/utils/PictureInPictureUtils.kt:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/hybrids/videoviewviewmanager/HybridVideoViewViewManager.kt:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/CustomMediaNotificationProvider.kt:1
- Orphaned file packages/react-native-video/ios/core/Utils/HLSManifestParser.swift:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/plugins/ReactNativeVideoPlugin.kt:1
- Orphaned file packages/react-native-video/src/core/video-view/VideoView.web.tsx:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/player/MediaItemUtils.kt:1
- Orphaned file packages/react-native-video/src/core/types/VideoConfig.ts:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/player/MediaSourceUtils.kt:1
- Orphaned file packages/drm-plugin/android/src/main/java/com/twg/videodrm/DRMManager/DRMManager.kt:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/VideoPlaybackCallback.kt:1
- Orphaned file packages/react-native-video/src/core/web/MediaSession.ts:1
- Orphaned file packages/react-native-video/android/src/main/java/com/twg/video/core/VideoError.kt:1
- Orphaned file packages/react-native-video/src/core/video-view/VideoViewProps.ts:1
- redundant comment packages/react-native-video/src/core/VideoPlayer.ts:219
- redundant comment packages/react-native-video/src/core/VideoPlayer.ts:228
- redundant comment packages/react-native-video/src/core/VideoPlayer.ts:261
- redundant comment packages/react-native-video/src/core/VideoPlayer.ts:375
- REDACTED
- REDACTED
- REDACTED
- Silent fallback default in catch packages/react-native-video/android/src/main/java/com/twg/video/core/services/playback/CustomMediaNotificationProvider.kt:94
- Silent fallback default in catch packages/react-native-video/android/src/main/java/com/twg/video/core/utils/VideoFileHelper.kt:47
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- ADRs not easily discoverable
- No SAST .github/workflows/cache-cleanup.yml:21
- Dependabot does not watch bun/gradle/bundler REDACTED:4
- No changelog
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 4 finding(s)
- Outdated: activesupport
- Outdated: cocoapods
- Skipped (documented): (unnamed test) packages/react-native-video/__tests__/expoPlugins.test.ts:316
- doc comments repeat the names packages/react-native-video/src/core/types/Events.ts:15
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fc73673ea9de458c9478702f8b1f0cd2/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fc73673ea9de458c9478702f8b1f0cd2/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude packages/drm-plugin/nitrogen/generated/android --exclude packages/drm-plugin/nitrogen/generated/ios --exclude packages/drm-plugin/nitrogen/generated/shared --exclude packages/react-native-video/android/src/paper --exclude packages/react-native-video/nitrogen/generated/android --exclude packages/react-native-video/nitrogen/generated/ios --exclude packages/react-native-video/nitrogen/generated/shared . | 45 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 93 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 5 file(s) — `docs/docusaurus.config.ts`, `packages/react-native-video/ios/core/HLSSubtitleInjector.swift`, `packages/react-native-video/ios/core/Utils/HLSManifestParser.swift`, `packages/react-native-video/src/core/hooks/useManagedInstance.ts`, `packages/react-native-video/src/index.tsx` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |