Executive summary
weekdayjast/MiracastReceiver falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 50.7 out of 100 and is rated Adequate, and all 23 of its critical findings are security problems.
Production Readiness, at 36.0, is the weakest lens and counts most in the score. The best first steps are adding an automated build and test pipeline and adding automated security scanning, each worth about 9.4 points. Raising Production Readiness to 70 would lift the score to about 61.2.
Seventeen weaknesses in the code could be used by an attacker. Six passwords or keys are open to anyone who can read the repository. Fixing the weaknesses the scanner points to and replacing each exposed password or key would close both risks.
The product code is 17,384 lines, about €18,000 to rebuild.
If Production Readiness rose from 36.0 to 70, the lowest score rated Strong, the score would rise from 50.7 to about 61.2.
Rebuild cost: about €18,000 · Estimate
| Cost to rebuild | €6,000 to €30,000, for 101 to 319 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.7 at a score of 51. 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: 17,384 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: which parts of the code depend on which
| uses → | 1 io.github.jqssun.airplay.bridge | 2 io.github.jqssun.airplay.renderer | 3 top.jast.miracastreceiver.airplay.AirPlayCapabilities | 4 top.jast.miracastreceiver.airplay.DmapParser | 5 top.jast.miracastreceiver.airplay.MlhlsRelay | 6 top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin | 7 top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer | 8 top.jast.miracastreceiver.cast.CastMdnsPacket | 9 top.jast.miracastreceiver.discovery | 10 top.jast.miracastreceiver.dlna.DlnaMediaRenderer | 11 top.jast.miracastreceiver.dlna.UpnpHttpServer | 12 top.jast.miracastreceiver.miracast.MiracastVideoRenderer | 13 top.jast.miracastreceiver.miracast.RtpReorderBuffer | 14 top.jast.miracastreceiver.miracast.TsDemuxer | 15 top.jast.miracastreceiver.miracast.WfdRootHelper | 16 top.jast.miracastreceiver.miracast.WifiDirectManager | 17 top.jast.miracastreceiver.service.ReceiverStatus | 18 top.jast.miracastreceiver.signaling | 19 top.jast.miracastreceiver.airplay.handshake | 20 top.jast.miracastreceiver.cast | 21 top.jast.miracastreceiver.castplus.CastPlusReceiver | 22 top.jast.miracastreceiver.dlna | 23 top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState | 24 top.jast.miracastreceiver.miracast.MiracastAudioPlayer | 25 top.jast.miracastreceiver.miracast.RtpReceiver | 26 top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec | 27 top.jast.miracastreceiver.miracast.TsDemuxer.Continuity | 28 top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult | 29 top.jast.miracastreceiver.ui.MirrorSurfaceRegistry | 30 top.jast.miracastreceiver.airplay | 31 top.jast.miracastreceiver.airplay.handshake.PairingKeys | 32 top.jast.miracastreceiver.castplus | 33 top.jast.miracastreceiver.castplus.CastPlusReceiver.Status | 34 top.jast.miracastreceiver.airplay.AirPlayState | 35 top.jast.miracastreceiver.airplay.AudioCodec | 36 top.jast.miracastreceiver.airplay.PhotoImageType | 37 top.jast.miracastreceiver.airplay.PhotoValidation | 38 top.jast.miracastreceiver.miracast | 39 top.jast.miracastreceiver.ui | 40 top.jast.miracastreceiver.service |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 io.github.jqssun.airplay.bridge | ||||||||||||||||||||||||||||||||||||||||
| 2 io.github.jqssun.airplay.renderer | ||||||||||||||||||||||||||||||||||||||||
| 3 top.jast.miracastreceiver.airplay.AirPlayCapabilities | ||||||||||||||||||||||||||||||||||||||||
| 4 top.jast.miracastreceiver.airplay.DmapParser | ||||||||||||||||||||||||||||||||||||||||
| 5 top.jast.miracastreceiver.airplay.MlhlsRelay | ||||||||||||||||||||||||||||||||||||||||
| 6 top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin | ||||||||||||||||||||||||||||||||||||||||
| 7 top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer | ||||||||||||||||||||||||||||||||||||||||
| 8 top.jast.miracastreceiver.cast.CastMdnsPacket | ||||||||||||||||||||||||||||||||||||||||
| 9 top.jast.miracastreceiver.discovery | ||||||||||||||||||||||||||||||||||||||||
| 10 top.jast.miracastreceiver.dlna.DlnaMediaRenderer | ||||||||||||||||||||||||||||||||||||||||
| 11 top.jast.miracastreceiver.dlna.UpnpHttpServer | ||||||||||||||||||||||||||||||||||||||||
| 12 top.jast.miracastreceiver.miracast.MiracastVideoRenderer | ||||||||||||||||||||||||||||||||||||||||
| 13 top.jast.miracastreceiver.miracast.RtpReorderBuffer | ||||||||||||||||||||||||||||||||||||||||
| 14 top.jast.miracastreceiver.miracast.TsDemuxer | ||||||||||||||||||||||||||||||||||||||||
| 15 top.jast.miracastreceiver.miracast.WfdRootHelper | ||||||||||||||||||||||||||||||||||||||||
| 16 top.jast.miracastreceiver.miracast.WifiDirectManager | ||||||||||||||||||||||||||||||||||||||||
| 17 top.jast.miracastreceiver.service.ReceiverStatus | ||||||||||||||||||||||||||||||||||||||||
| 18 top.jast.miracastreceiver.signaling | ||||||||||||||||||||||||||||||||||||||||
| 19 top.jast.miracastreceiver.airplay.handshake | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 top.jast.miracastreceiver.cast | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 top.jast.miracastreceiver.castplus.CastPlusReceiver | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 top.jast.miracastreceiver.dlna | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState | 5 | |||||||||||||||||||||||||||||||||||||||
| 24 top.jast.miracastreceiver.miracast.MiracastAudioPlayer | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 top.jast.miracastreceiver.miracast.RtpReceiver | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec | 2 | |||||||||||||||||||||||||||||||||||||||
| 27 top.jast.miracastreceiver.miracast.TsDemuxer.Continuity | 3 | |||||||||||||||||||||||||||||||||||||||
| 28 top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult | 5 | |||||||||||||||||||||||||||||||||||||||
| 29 top.jast.miracastreceiver.ui.MirrorSurfaceRegistry | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 top.jast.miracastreceiver.airplay | 1 | 1 | 2 | 2 | 1 | 10 | ||||||||||||||||||||||||||||||||||
| 31 top.jast.miracastreceiver.airplay.handshake.PairingKeys | 1 | |||||||||||||||||||||||||||||||||||||||
| 32 top.jast.miracastreceiver.castplus | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 top.jast.miracastreceiver.castplus.CastPlusReceiver.Status | 11 | |||||||||||||||||||||||||||||||||||||||
| 34 top.jast.miracastreceiver.airplay.AirPlayState | 4 | |||||||||||||||||||||||||||||||||||||||
| 35 top.jast.miracastreceiver.airplay.AudioCodec | 3 | |||||||||||||||||||||||||||||||||||||||
| 36 top.jast.miracastreceiver.airplay.PhotoImageType | 2 | |||||||||||||||||||||||||||||||||||||||
| 37 top.jast.miracastreceiver.airplay.PhotoValidation | 3 | |||||||||||||||||||||||||||||||||||||||
| 38 top.jast.miracastreceiver.miracast | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 39 top.jast.miracastreceiver.ui | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 40 top.jast.miracastreceiver.service | 3 | 2 | 3 | 1 | 1 | 2 |
19→6 top.jast.miracastreceiver.airplay.handshake uses top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.airplay.handshake uses a type in top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin.
- The types involved
top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin→top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin.Result
- Direction
- top.jast.miracastreceiver.airplay.handshake uses top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin, so a change to top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin can break top.jast.miracastreceiver.airplay.handshake, while a change to top.jast.miracastreceiver.airplay.handshake can't break top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPin.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.handshake uses a module listed above it, which is the healthy direction.
19→7 top.jast.miracastreceiver.airplay.handshake uses top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.airplay.handshake uses a type in top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer.
- The types involved
top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer→top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer.Configtop.jast.miracastreceiver.airplay.handshake.MirrorStreamServer→top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer.Item
- Direction
- top.jast.miracastreceiver.airplay.handshake uses top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer, so a change to top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer can break top.jast.miracastreceiver.airplay.handshake, while a change to top.jast.miracastreceiver.airplay.handshake can't break top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.handshake uses a module listed above it, which is the healthy direction.
19→30 top.jast.miracastreceiver.airplay.handshake uses top.jast.miracastreceiver.airplay part of a loop✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.airplay.handshake uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.airplay.handshake.MirrorStreamServer→top.jast.miracastreceiver.airplay.VideoDecoder
- Direction
- top.jast.miracastreceiver.airplay.handshake uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.airplay.handshake, while a change to top.jast.miracastreceiver.airplay.handshake can't break top.jast.miracastreceiver.airplay.
- 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.
20→8 top.jast.miracastreceiver.cast uses top.jast.miracastreceiver.cast.CastMdnsPacket✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.cast uses a type in top.jast.miracastreceiver.cast.CastMdnsPacket.
- The types involved
top.jast.miracastreceiver.cast.CastMdnsPacket→top.jast.miracastreceiver.cast.CastMdnsPacket.Query
- Direction
- top.jast.miracastreceiver.cast uses top.jast.miracastreceiver.cast.CastMdnsPacket, so a change to top.jast.miracastreceiver.cast.CastMdnsPacket can break top.jast.miracastreceiver.cast, while a change to top.jast.miracastreceiver.cast can't break top.jast.miracastreceiver.cast.CastMdnsPacket.
- Position
- Below the diagonal: top.jast.miracastreceiver.cast uses a module listed above it, which is the healthy direction.
21→32 top.jast.miracastreceiver.castplus.CastPlusReceiver uses top.jast.miracastreceiver.castplus part of a loop✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.castplus.CastPlusReceiver uses a type in top.jast.miracastreceiver.castplus.
- The types involved
top.jast.miracastreceiver.castplus.CastPlusReceiver.Companion→top.jast.miracastreceiver.castplus.CastPlusReceiver
- Direction
- top.jast.miracastreceiver.castplus.CastPlusReceiver uses top.jast.miracastreceiver.castplus, so a change to top.jast.miracastreceiver.castplus can break top.jast.miracastreceiver.castplus.CastPlusReceiver, while a change to top.jast.miracastreceiver.castplus.CastPlusReceiver can't break top.jast.miracastreceiver.castplus.
- 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.
22→10 top.jast.miracastreceiver.dlna uses top.jast.miracastreceiver.dlna.DlnaMediaRenderer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.dlna uses a type in top.jast.miracastreceiver.dlna.DlnaMediaRenderer.
- The types involved
top.jast.miracastreceiver.dlna.DlnaMediaRenderer→top.jast.miracastreceiver.dlna.DlnaMediaRenderer.MediaState
- Direction
- top.jast.miracastreceiver.dlna uses top.jast.miracastreceiver.dlna.DlnaMediaRenderer, so a change to top.jast.miracastreceiver.dlna.DlnaMediaRenderer can break top.jast.miracastreceiver.dlna, while a change to top.jast.miracastreceiver.dlna can't break top.jast.miracastreceiver.dlna.DlnaMediaRenderer.
- Position
- Below the diagonal: top.jast.miracastreceiver.dlna uses a module listed above it, which is the healthy direction.
22→11 top.jast.miracastreceiver.dlna uses top.jast.miracastreceiver.dlna.UpnpHttpServer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.dlna uses a type in top.jast.miracastreceiver.dlna.UpnpHttpServer.
- The types involved
top.jast.miracastreceiver.dlna.UpnpHttpServer→top.jast.miracastreceiver.dlna.UpnpHttpServer.EventSubscription
- Direction
- top.jast.miracastreceiver.dlna uses top.jast.miracastreceiver.dlna.UpnpHttpServer, so a change to top.jast.miracastreceiver.dlna.UpnpHttpServer can break top.jast.miracastreceiver.dlna, while a change to top.jast.miracastreceiver.dlna can't break top.jast.miracastreceiver.dlna.UpnpHttpServer.
- Position
- Below the diagonal: top.jast.miracastreceiver.dlna uses a module listed above it, which is the healthy direction.
23→10 top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState uses top.jast.miracastreceiver.dlna.DlnaMediaRenderer✕
- Connections
- 5 pairs of types, where a type in top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState uses a type in top.jast.miracastreceiver.dlna.DlnaMediaRenderer.
- The types involved
top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState.NO_MEDIA_PRESENT→top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportStatetop.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState.PAUSED_PLAYBACK→top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportStatetop.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState.PLAYING→top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportStatetop.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState.STOPPED→top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportStatetop.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState.TRANSITIONING→top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState
- Direction
- top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState uses top.jast.miracastreceiver.dlna.DlnaMediaRenderer, so a change to top.jast.miracastreceiver.dlna.DlnaMediaRenderer can break top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState, while a change to top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState can't break top.jast.miracastreceiver.dlna.DlnaMediaRenderer.
- Position
- Below the diagonal: top.jast.miracastreceiver.dlna.DlnaMediaRenderer.TransportState uses a module listed above it, which is the healthy direction.
24→14 top.jast.miracastreceiver.miracast.MiracastAudioPlayer uses top.jast.miracastreceiver.miracast.TsDemuxer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast.MiracastAudioPlayer uses a type in top.jast.miracastreceiver.miracast.TsDemuxer.
- The types involved
top.jast.miracastreceiver.miracast.MiracastAudioPlayer.AudioPes→top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec
- Direction
- top.jast.miracastreceiver.miracast.MiracastAudioPlayer uses top.jast.miracastreceiver.miracast.TsDemuxer, so a change to top.jast.miracastreceiver.miracast.TsDemuxer can break top.jast.miracastreceiver.miracast.MiracastAudioPlayer, while a change to top.jast.miracastreceiver.miracast.MiracastAudioPlayer can't break top.jast.miracastreceiver.miracast.TsDemuxer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast.MiracastAudioPlayer uses a module listed above it, which is the healthy direction.
25→38 top.jast.miracastreceiver.miracast.RtpReceiver uses top.jast.miracastreceiver.miracast part of a loop✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast.RtpReceiver uses a type in top.jast.miracastreceiver.miracast.
- The types involved
top.jast.miracastreceiver.miracast.RtpReceiver.Companion→top.jast.miracastreceiver.miracast.RtpReceiver
- Direction
- top.jast.miracastreceiver.miracast.RtpReceiver uses top.jast.miracastreceiver.miracast, so a change to top.jast.miracastreceiver.miracast can break top.jast.miracastreceiver.miracast.RtpReceiver, while a change to top.jast.miracastreceiver.miracast.RtpReceiver can't break top.jast.miracastreceiver.miracast.
- 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.
26→14 top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec uses top.jast.miracastreceiver.miracast.TsDemuxer✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec uses a type in top.jast.miracastreceiver.miracast.TsDemuxer.
- The types involved
top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec.AAC_ADTS→top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodectop.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec.LPCM→top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec
- Direction
- top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec uses top.jast.miracastreceiver.miracast.TsDemuxer, so a change to top.jast.miracastreceiver.miracast.TsDemuxer can break top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec, while a change to top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec can't break top.jast.miracastreceiver.miracast.TsDemuxer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodec uses a module listed above it, which is the healthy direction.
27→14 top.jast.miracastreceiver.miracast.TsDemuxer.Continuity uses top.jast.miracastreceiver.miracast.TsDemuxer✕
- Connections
- 3 pairs of types, where a type in top.jast.miracastreceiver.miracast.TsDemuxer.Continuity uses a type in top.jast.miracastreceiver.miracast.TsDemuxer.
- The types involved
top.jast.miracastreceiver.miracast.TsDemuxer.Continuity.DUPLICATE→top.jast.miracastreceiver.miracast.TsDemuxer.Continuitytop.jast.miracastreceiver.miracast.TsDemuxer.Continuity.GAP→top.jast.miracastreceiver.miracast.TsDemuxer.Continuitytop.jast.miracastreceiver.miracast.TsDemuxer.Continuity.OK→top.jast.miracastreceiver.miracast.TsDemuxer.Continuity
- Direction
- top.jast.miracastreceiver.miracast.TsDemuxer.Continuity uses top.jast.miracastreceiver.miracast.TsDemuxer, so a change to top.jast.miracastreceiver.miracast.TsDemuxer can break top.jast.miracastreceiver.miracast.TsDemuxer.Continuity, while a change to top.jast.miracastreceiver.miracast.TsDemuxer.Continuity can't break top.jast.miracastreceiver.miracast.TsDemuxer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast.TsDemuxer.Continuity uses a module listed above it, which is the healthy direction.
28→15 top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult uses top.jast.miracastreceiver.miracast.WfdRootHelper✕
- Connections
- 5 pairs of types, where a type in top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult uses a type in top.jast.miracastreceiver.miracast.WfdRootHelper.
- The types involved
top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult.COMMAND_FAILED→top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResulttop.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult.COMMAND_SENT→top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResulttop.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult.HELPER_MISSING→top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResulttop.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult.ROOT_UNAVAILABLE→top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResulttop.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult.SOCKET_UNAVAILABLE→top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult
- Direction
- top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult uses top.jast.miracastreceiver.miracast.WfdRootHelper, so a change to top.jast.miracastreceiver.miracast.WfdRootHelper can break top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult, while a change to top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult can't break top.jast.miracastreceiver.miracast.WfdRootHelper.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult uses a module listed above it, which is the healthy direction.
29→39 top.jast.miracastreceiver.ui.MirrorSurfaceRegistry uses top.jast.miracastreceiver.ui part of a loop✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.ui.MirrorSurfaceRegistry uses a type in top.jast.miracastreceiver.ui.
- The types involved
top.jast.miracastreceiver.ui.MirrorSurfaceRegistry.Publication→top.jast.miracastreceiver.ui.MirrorSurfaceSource
- Direction
- top.jast.miracastreceiver.ui.MirrorSurfaceRegistry uses top.jast.miracastreceiver.ui, so a change to top.jast.miracastreceiver.ui can break top.jast.miracastreceiver.ui.MirrorSurfaceRegistry, while a change to top.jast.miracastreceiver.ui.MirrorSurfaceRegistry can't break top.jast.miracastreceiver.ui.
- 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.
30→1 top.jast.miracastreceiver.airplay uses io.github.jqssun.airplay.bridge✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.airplay uses a type in io.github.jqssun.airplay.bridge.
- The types involved
top.jast.miracastreceiver.airplay.UxPlayReceiver→io.github.jqssun.airplay.bridge.RaopCallbackHandler
- Direction
- top.jast.miracastreceiver.airplay uses io.github.jqssun.airplay.bridge, so a change to io.github.jqssun.airplay.bridge can break top.jast.miracastreceiver.airplay, while a change to top.jast.miracastreceiver.airplay can't break io.github.jqssun.airplay.bridge.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay uses a module listed above it, which is the healthy direction.
30→2 top.jast.miracastreceiver.airplay uses io.github.jqssun.airplay.renderer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.airplay uses a type in io.github.jqssun.airplay.renderer.
- The types involved
top.jast.miracastreceiver.airplay.UxPlayReceiver→io.github.jqssun.airplay.renderer.VideoRenderer
- Direction
- top.jast.miracastreceiver.airplay uses io.github.jqssun.airplay.renderer, so a change to io.github.jqssun.airplay.renderer can break top.jast.miracastreceiver.airplay, while a change to top.jast.miracastreceiver.airplay can't break io.github.jqssun.airplay.renderer.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay uses a module listed above it, which is the healthy direction.
30→3 top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.AirPlayCapabilities✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.airplay uses a type in top.jast.miracastreceiver.airplay.AirPlayCapabilities.
- The types involved
top.jast.miracastreceiver.airplay.AirPlayCapabilities→top.jast.miracastreceiver.airplay.AirPlayCapabilities.HevcDecodertop.jast.miracastreceiver.airplay.AirPlayCapabilities→top.jast.miracastreceiver.airplay.AirPlayCapabilities.Selection
- Direction
- top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.AirPlayCapabilities, so a change to top.jast.miracastreceiver.airplay.AirPlayCapabilities can break top.jast.miracastreceiver.airplay, while a change to top.jast.miracastreceiver.airplay can't break top.jast.miracastreceiver.airplay.AirPlayCapabilities.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay uses a module listed above it, which is the healthy direction.
30→4 top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.DmapParser✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.airplay uses a type in top.jast.miracastreceiver.airplay.DmapParser.
- The types involved
top.jast.miracastreceiver.airplay.DmapParser→top.jast.miracastreceiver.airplay.DmapParser.Metadatatop.jast.miracastreceiver.airplay.DmapParser→top.jast.miracastreceiver.airplay.DmapParser.MutableMetadata
- Direction
- top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.DmapParser, so a change to top.jast.miracastreceiver.airplay.DmapParser can break top.jast.miracastreceiver.airplay, while a change to top.jast.miracastreceiver.airplay can't break top.jast.miracastreceiver.airplay.DmapParser.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay uses a module listed above it, which is the healthy direction.
30→5 top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.MlhlsRelay✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.airplay uses a type in top.jast.miracastreceiver.airplay.MlhlsRelay.
- The types involved
top.jast.miracastreceiver.airplay.MlhlsRelay→top.jast.miracastreceiver.airplay.MlhlsRelay.Reply
- Direction
- top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.MlhlsRelay, so a change to top.jast.miracastreceiver.airplay.MlhlsRelay can break top.jast.miracastreceiver.airplay, while a change to top.jast.miracastreceiver.airplay can't break top.jast.miracastreceiver.airplay.MlhlsRelay.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay uses a module listed above it, which is the healthy direction.
30→19 top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.handshake✕
- Connections
- 10 pairs of types, where a type in top.jast.miracastreceiver.airplay uses a type in top.jast.miracastreceiver.airplay.handshake.
- The types involved
top.jast.miracastreceiver.airplay.AirPlayReceiver→top.jast.miracastreceiver.airplay.handshake.AirPlayNtpClienttop.jast.miracastreceiver.airplay.AirPlayReceiver→top.jast.miracastreceiver.airplay.handshake.AudioStreamServertop.jast.miracastreceiver.airplay.AirPlayReceiver→top.jast.miracastreceiver.airplay.handshake.BufferedAudioServertop.jast.miracastreceiver.airplay.AirPlayReceiver→top.jast.miracastreceiver.airplay.handshake.MirrorStreamServertop.jast.miracastreceiver.airplay.AirPlayReceiver→top.jast.miracastreceiver.airplay.handshake.PairingStoretop.jast.miracastreceiver.airplay.AudioPlayer→top.jast.miracastreceiver.airplay.handshake.AlacDecodertop.jast.miracastreceiver.airplay.RtspHandler→top.jast.miracastreceiver.airplay.handshake.FairPlaytop.jast.miracastreceiver.airplay.RtspHandler→top.jast.miracastreceiver.airplay.handshake.LegacyPairSetupPintop.jast.miracastreceiver.airplay.RtspHandler→top.jast.miracastreceiver.airplay.handshake.PairingSessiontop.jast.miracastreceiver.airplay.RtspHandler→top.jast.miracastreceiver.airplay.handshake.PairingStore
- Direction
- top.jast.miracastreceiver.airplay uses top.jast.miracastreceiver.airplay.handshake, so a change to top.jast.miracastreceiver.airplay.handshake can break top.jast.miracastreceiver.airplay, while a change to top.jast.miracastreceiver.airplay can't break top.jast.miracastreceiver.airplay.handshake.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay uses a module listed above it, which is the healthy direction.
31→19 top.jast.miracastreceiver.airplay.handshake.PairingKeys uses top.jast.miracastreceiver.airplay.handshake✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.airplay.handshake.PairingKeys uses a type in top.jast.miracastreceiver.airplay.handshake.
- The types involved
top.jast.miracastreceiver.airplay.handshake.PairingKeys.Companion→top.jast.miracastreceiver.airplay.handshake.PairingKeys
- Direction
- top.jast.miracastreceiver.airplay.handshake.PairingKeys uses top.jast.miracastreceiver.airplay.handshake, so a change to top.jast.miracastreceiver.airplay.handshake can break top.jast.miracastreceiver.airplay.handshake.PairingKeys, while a change to top.jast.miracastreceiver.airplay.handshake.PairingKeys can't break top.jast.miracastreceiver.airplay.handshake.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.handshake.PairingKeys uses a module listed above it, which is the healthy direction.
32→21 top.jast.miracastreceiver.castplus uses top.jast.miracastreceiver.castplus.CastPlusReceiver✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.castplus uses a type in top.jast.miracastreceiver.castplus.CastPlusReceiver.
- The types involved
top.jast.miracastreceiver.castplus.CastPlusReceiver→top.jast.miracastreceiver.castplus.CastPlusReceiver.State
- Direction
- top.jast.miracastreceiver.castplus uses top.jast.miracastreceiver.castplus.CastPlusReceiver, so a change to top.jast.miracastreceiver.castplus.CastPlusReceiver can break top.jast.miracastreceiver.castplus, while a change to top.jast.miracastreceiver.castplus can't break top.jast.miracastreceiver.castplus.CastPlusReceiver.
- Position
- Below the diagonal: top.jast.miracastreceiver.castplus uses a module listed above it, which is the healthy direction.
33→21 top.jast.miracastreceiver.castplus.CastPlusReceiver.Status uses top.jast.miracastreceiver.castplus.CastPlusReceiver✕
- Connections
- 11 pairs of types, where a type in top.jast.miracastreceiver.castplus.CastPlusReceiver.Status uses a type in top.jast.miracastreceiver.castplus.CastPlusReceiver.
- The types involved
top.jast.miracastreceiver.castplus.CastPlusReceiver.Status.CONNECTING→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.DISCONNECTING→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.ERROR→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.OFF→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.PAIRING→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.PAUSED→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.PERMISSION_REQUIRED→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.PLAYING→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.READY→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.STARTING→top.jast.miracastreceiver.castplus.CastPlusReceiver.Statustop.jast.miracastreceiver.castplus.CastPlusReceiver.Status.UNSUPPORTED→top.jast.miracastreceiver.castplus.CastPlusReceiver.Status
- Direction
- top.jast.miracastreceiver.castplus.CastPlusReceiver.Status uses top.jast.miracastreceiver.castplus.CastPlusReceiver, so a change to top.jast.miracastreceiver.castplus.CastPlusReceiver can break top.jast.miracastreceiver.castplus.CastPlusReceiver.Status, while a change to top.jast.miracastreceiver.castplus.CastPlusReceiver.Status can't break top.jast.miracastreceiver.castplus.CastPlusReceiver.
- Position
- Below the diagonal: top.jast.miracastreceiver.castplus.CastPlusReceiver.Status uses a module listed above it, which is the healthy direction.
34→30 top.jast.miracastreceiver.airplay.AirPlayState uses top.jast.miracastreceiver.airplay✕
- Connections
- 4 pairs of types, where a type in top.jast.miracastreceiver.airplay.AirPlayState uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.airplay.AirPlayState.ADVERTISING→top.jast.miracastreceiver.airplay.AirPlayStatetop.jast.miracastreceiver.airplay.AirPlayState.CONNECTED→top.jast.miracastreceiver.airplay.AirPlayStatetop.jast.miracastreceiver.airplay.AirPlayState.DISABLED→top.jast.miracastreceiver.airplay.AirPlayStatetop.jast.miracastreceiver.airplay.AirPlayState.ERROR→top.jast.miracastreceiver.airplay.AirPlayState
- Direction
- top.jast.miracastreceiver.airplay.AirPlayState uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.airplay.AirPlayState, while a change to top.jast.miracastreceiver.airplay.AirPlayState can't break top.jast.miracastreceiver.airplay.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.AirPlayState uses a module listed above it, which is the healthy direction.
35→30 top.jast.miracastreceiver.airplay.AudioCodec uses top.jast.miracastreceiver.airplay✕
- Connections
- 3 pairs of types, where a type in top.jast.miracastreceiver.airplay.AudioCodec uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.airplay.AudioCodec.AAC_ELD→top.jast.miracastreceiver.airplay.AudioCodectop.jast.miracastreceiver.airplay.AudioCodec.ALAC→top.jast.miracastreceiver.airplay.AudioCodectop.jast.miracastreceiver.airplay.AudioCodec.UNKNOWN→top.jast.miracastreceiver.airplay.AudioCodec
- Direction
- top.jast.miracastreceiver.airplay.AudioCodec uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.airplay.AudioCodec, while a change to top.jast.miracastreceiver.airplay.AudioCodec can't break top.jast.miracastreceiver.airplay.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.AudioCodec uses a module listed above it, which is the healthy direction.
36→30 top.jast.miracastreceiver.airplay.PhotoImageType uses top.jast.miracastreceiver.airplay✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.airplay.PhotoImageType uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.airplay.PhotoImageType.JPEG→top.jast.miracastreceiver.airplay.PhotoImageTypetop.jast.miracastreceiver.airplay.PhotoImageType.PNG→top.jast.miracastreceiver.airplay.PhotoImageType
- Direction
- top.jast.miracastreceiver.airplay.PhotoImageType uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.airplay.PhotoImageType, while a change to top.jast.miracastreceiver.airplay.PhotoImageType can't break top.jast.miracastreceiver.airplay.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.PhotoImageType uses a module listed above it, which is the healthy direction.
37→30 top.jast.miracastreceiver.airplay.PhotoValidation uses top.jast.miracastreceiver.airplay✕
- Connections
- 3 pairs of types, where a type in top.jast.miracastreceiver.airplay.PhotoValidation uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.airplay.PhotoValidation.Invalid→top.jast.miracastreceiver.airplay.PhotoValidationtop.jast.miracastreceiver.airplay.PhotoValidation.Valid→top.jast.miracastreceiver.airplay.PhotoImageTypetop.jast.miracastreceiver.airplay.PhotoValidation.Valid→top.jast.miracastreceiver.airplay.PhotoValidation
- Direction
- top.jast.miracastreceiver.airplay.PhotoValidation uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.airplay.PhotoValidation, while a change to top.jast.miracastreceiver.airplay.PhotoValidation can't break top.jast.miracastreceiver.airplay.
- Position
- Below the diagonal: top.jast.miracastreceiver.airplay.PhotoValidation uses a module listed above it, which is the healthy direction.
38→12 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.MiracastVideoRenderer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.MiracastVideoRenderer.
- The types involved
top.jast.miracastreceiver.miracast.MiracastVideoRenderer→top.jast.miracastreceiver.miracast.MiracastVideoRenderer.AccessUnit
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.MiracastVideoRenderer, so a change to top.jast.miracastreceiver.miracast.MiracastVideoRenderer can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.MiracastVideoRenderer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→13 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.RtpReorderBuffer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.RtpReorderBuffer.
- The types involved
top.jast.miracastreceiver.miracast.RtpReorderBuffer→top.jast.miracastreceiver.miracast.RtpReorderBuffer.Pending
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.RtpReorderBuffer, so a change to top.jast.miracastreceiver.miracast.RtpReorderBuffer can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.RtpReorderBuffer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→14 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.TsDemuxer✕
- Connections
- 3 pairs of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.TsDemuxer.
- The types involved
top.jast.miracastreceiver.miracast.MiracastAudioPlayer→top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodectop.jast.miracastreceiver.miracast.TsDemuxer→top.jast.miracastreceiver.miracast.TsDemuxer.AudioCodectop.jast.miracastreceiver.miracast.TsDemuxer→top.jast.miracastreceiver.miracast.TsDemuxer.PesAssembler
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.TsDemuxer, so a change to top.jast.miracastreceiver.miracast.TsDemuxer can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.TsDemuxer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→15 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.WfdRootHelper✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.WfdRootHelper.
- The types involved
top.jast.miracastreceiver.miracast.WfdRootHelper→top.jast.miracastreceiver.miracast.WfdRootHelper.AdvertiseResult
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.WfdRootHelper, so a change to top.jast.miracastreceiver.miracast.WfdRootHelper can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.WfdRootHelper.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→16 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.WifiDirectManager✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.WifiDirectManager.
- The types involved
top.jast.miracastreceiver.miracast.WifiDirectManager→top.jast.miracastreceiver.miracast.WifiDirectManager.StartupState
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.WifiDirectManager, so a change to top.jast.miracastreceiver.miracast.WifiDirectManager can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.WifiDirectManager.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→24 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.MiracastAudioPlayer✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.MiracastAudioPlayer.
- The types involved
top.jast.miracastreceiver.miracast.MiracastAudioPlayer→top.jast.miracastreceiver.miracast.MiracastAudioPlayer.AudioPes
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.MiracastAudioPlayer, so a change to top.jast.miracastreceiver.miracast.MiracastAudioPlayer can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.MiracastAudioPlayer.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→25 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.RtpReceiver✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.miracast.RtpReceiver.
- The types involved
top.jast.miracastreceiver.miracast.RtpReceiver→top.jast.miracastreceiver.miracast.RtpReceiver.Payload
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.miracast.RtpReceiver, so a change to top.jast.miracastreceiver.miracast.RtpReceiver can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.miracast.RtpReceiver.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
38→30 top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.airplay✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.miracast uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.miracast.MiracastVideoRenderer→top.jast.miracastreceiver.airplay.VideoDecoder
- Direction
- top.jast.miracastreceiver.miracast uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.miracast, while a change to top.jast.miracastreceiver.miracast can't break top.jast.miracastreceiver.airplay.
- Position
- Below the diagonal: top.jast.miracastreceiver.miracast uses a module listed above it, which is the healthy direction.
39→9 top.jast.miracastreceiver.ui uses top.jast.miracastreceiver.discovery✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.ui uses a type in top.jast.miracastreceiver.discovery.
- The types involved
top.jast.miracastreceiver.ui.MainActivity→top.jast.miracastreceiver.discovery.DeviceInfoProvidertop.jast.miracastreceiver.ui.MainActivity→top.jast.miracastreceiver.discovery.MdnsAdvertiser
- Direction
- top.jast.miracastreceiver.ui uses top.jast.miracastreceiver.discovery, so a change to top.jast.miracastreceiver.discovery can break top.jast.miracastreceiver.ui, while a change to top.jast.miracastreceiver.ui can't break top.jast.miracastreceiver.discovery.
- Position
- Below the diagonal: top.jast.miracastreceiver.ui uses a module listed above it, which is the healthy direction.
39→29 top.jast.miracastreceiver.ui uses top.jast.miracastreceiver.ui.MirrorSurfaceRegistry✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.ui uses a type in top.jast.miracastreceiver.ui.MirrorSurfaceRegistry.
- The types involved
top.jast.miracastreceiver.ui.MirrorSurfaceRegistry→top.jast.miracastreceiver.ui.MirrorSurfaceRegistry.Publication
- Direction
- top.jast.miracastreceiver.ui uses top.jast.miracastreceiver.ui.MirrorSurfaceRegistry, so a change to top.jast.miracastreceiver.ui.MirrorSurfaceRegistry can break top.jast.miracastreceiver.ui, while a change to top.jast.miracastreceiver.ui can't break top.jast.miracastreceiver.ui.MirrorSurfaceRegistry.
- Position
- Below the diagonal: top.jast.miracastreceiver.ui uses a module listed above it, which is the healthy direction.
39→32 top.jast.miracastreceiver.ui uses top.jast.miracastreceiver.castplus✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.ui uses a type in top.jast.miracastreceiver.castplus.
- The types involved
top.jast.miracastreceiver.ui.CastPlusPlayerActivity→top.jast.miracastreceiver.castplus.CastPlusReceivertop.jast.miracastreceiver.ui.ConnectActivity→top.jast.miracastreceiver.castplus.CastPlusReceiver
- Direction
- top.jast.miracastreceiver.ui uses top.jast.miracastreceiver.castplus, so a change to top.jast.miracastreceiver.castplus can break top.jast.miracastreceiver.ui, while a change to top.jast.miracastreceiver.ui can't break top.jast.miracastreceiver.castplus.
- Position
- Below the diagonal: top.jast.miracastreceiver.ui uses a module listed above it, which is the healthy direction.
40→17 top.jast.miracastreceiver.service uses top.jast.miracastreceiver.service.ReceiverStatus✕
- Connections
- 3 pairs of types, where a type in top.jast.miracastreceiver.service uses a type in top.jast.miracastreceiver.service.ReceiverStatus.
- The types involved
top.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.service.ReceiverStatus.Miracasttop.jast.miracastreceiver.service.ReceiverStatus→top.jast.miracastreceiver.service.ReceiverStatus.Miracasttop.jast.miracastreceiver.service.ReceiverStatus→top.jast.miracastreceiver.service.ReceiverStatus.Service
- Direction
- top.jast.miracastreceiver.service uses top.jast.miracastreceiver.service.ReceiverStatus, so a change to top.jast.miracastreceiver.service.ReceiverStatus can break top.jast.miracastreceiver.service, while a change to top.jast.miracastreceiver.service can't break top.jast.miracastreceiver.service.ReceiverStatus.
- Position
- Below the diagonal: top.jast.miracastreceiver.service uses a module listed above it, which is the healthy direction.
40→20 top.jast.miracastreceiver.service uses top.jast.miracastreceiver.cast✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.service uses a type in top.jast.miracastreceiver.cast.
- The types involved
top.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.cast.CastPlayerBridgetop.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.cast.GoogleCastReceiver
- Direction
- top.jast.miracastreceiver.service uses top.jast.miracastreceiver.cast, so a change to top.jast.miracastreceiver.cast can break top.jast.miracastreceiver.service, while a change to top.jast.miracastreceiver.service can't break top.jast.miracastreceiver.cast.
- Position
- Below the diagonal: top.jast.miracastreceiver.service uses a module listed above it, which is the healthy direction.
40→22 top.jast.miracastreceiver.service uses top.jast.miracastreceiver.dlna✕
- Connections
- 3 pairs of types, where a type in top.jast.miracastreceiver.service uses a type in top.jast.miracastreceiver.dlna.
- The types involved
top.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.dlna.DlnaMediaRenderertop.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.dlna.SsdpServertop.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.dlna.UpnpHttpServer
- Direction
- top.jast.miracastreceiver.service uses top.jast.miracastreceiver.dlna, so a change to top.jast.miracastreceiver.dlna can break top.jast.miracastreceiver.service, while a change to top.jast.miracastreceiver.service can't break top.jast.miracastreceiver.dlna.
- Position
- Below the diagonal: top.jast.miracastreceiver.service uses a module listed above it, which is the healthy direction.
40→30 top.jast.miracastreceiver.service uses top.jast.miracastreceiver.airplay✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.service uses a type in top.jast.miracastreceiver.airplay.
- The types involved
top.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.airplay.AirPlayReceiver
- Direction
- top.jast.miracastreceiver.service uses top.jast.miracastreceiver.airplay, so a change to top.jast.miracastreceiver.airplay can break top.jast.miracastreceiver.service, while a change to top.jast.miracastreceiver.service can't break top.jast.miracastreceiver.airplay.
- Position
- Below the diagonal: top.jast.miracastreceiver.service uses a module listed above it, which is the healthy direction.
40→32 top.jast.miracastreceiver.service uses top.jast.miracastreceiver.castplus✕
- Connections
- 1 pair of types, where a type in top.jast.miracastreceiver.service uses a type in top.jast.miracastreceiver.castplus.
- The types involved
top.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.castplus.CastPlusReceiver
- Direction
- top.jast.miracastreceiver.service uses top.jast.miracastreceiver.castplus, so a change to top.jast.miracastreceiver.castplus can break top.jast.miracastreceiver.service, while a change to top.jast.miracastreceiver.service can't break top.jast.miracastreceiver.castplus.
- Position
- Below the diagonal: top.jast.miracastreceiver.service uses a module listed above it, which is the healthy direction.
40→38 top.jast.miracastreceiver.service uses top.jast.miracastreceiver.miracast✕
- Connections
- 2 pairs of types, where a type in top.jast.miracastreceiver.service uses a type in top.jast.miracastreceiver.miracast.
- The types involved
top.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.miracast.WfdServertop.jast.miracastreceiver.service.CastReceiverService→top.jast.miracastreceiver.miracast.WifiDirectManager
- Direction
- top.jast.miracastreceiver.service uses top.jast.miracastreceiver.miracast, so a change to top.jast.miracastreceiver.miracast can break top.jast.miracastreceiver.service, while a change to top.jast.miracastreceiver.service can't break top.jast.miracastreceiver.miracast.
- Position
- Below the diagonal: top.jast.miracastreceiver.service 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 18 | High / Critical |
| A07:2025 — Authentication Failures | 7 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Add a CI workflow that builds and runs the test suite on every push/PR. | +9.4 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +9.4 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. | +3.1 pts | Low | ADR Quality |
| Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (6). | +2.6 pts | Low | Secrets (history) |
| Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). | +4.2 pts | Medium | Static Analysis (SAST) |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +3.0 pts | Medium | Architecture documentation |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. | +1.0 pts | Low | Project Cohesion |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Secrets (history): REDACTED: REDACTED |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt | 7.0 | Mixed | Cyclomatic Complexity: PlayerActivity.dispatchKeyEvent (cyclomatic 20) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt | 7.0 | Mixed | Cyclomatic Complexity: RtspHandler.handleMirrorSetup (cyclomatic 16) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/UpnpHttpServer.kt | 7.1 | Mixed | Cyclomatic Complexity: UpnpHttpServer.handleAvTransportControl (cyclomatic 28) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/TsDemuxer.kt | 7.2 | Mixed | Cyclomatic Complexity: TsDemuxer.handlePacket (cyclomatic 16) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AirPlayHlsPlayer.kt | 7.4 | Mixed | Cyclomatic Complexity: AirPlayHlsPlayer.play (cyclomatic 24) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/AudioStreamServer.kt | 7.4 | Mixed | Code Duplication: Edited copy of a member (41 corresponding lines) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/cast/CastSession.kt | 7.8 | Mixed | Cyclomatic Complexity: CastSession.handle (cyclomatic 47) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/VideoDecoder.kt | 7.8 | Mixed | Cyclomatic Complexity: VideoDecoder.parseSpsResolution (cyclomatic 27) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/settings/NameSetupServer.kt | 7.8 | Mixed | Cyclomatic Complexity: NameSetupServer.handle (cyclomatic 21) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/RtpReceiver.kt | 7.8 | Mixed | Cyclomatic Complexity: RtpReceiver.start (cyclomatic 18) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/SdpParser.kt | 7.8 | Mixed | Cyclomatic Complexity: SdpParser.parse (cyclomatic 16) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/MirrorStreamServer.kt | 7.8 | Mixed | Cognitive Complexity: MirrorStreamServer.runReader (cognitive 18) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/NowPlayingInfo.kt | 7.8 | Mixed | Cognitive Complexity: DmapParser.walk (cognitive 17) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/SsdpServer.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (31 corresponding lines) |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/utils/NetworkUtils.kt | 7.8 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/MainActivity.kt | 8.5 | Near-clean | Cyclomatic Complexity: MainActivity.updateStatus (cyclomatic 29) |
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 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 51 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, 107 of 113 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
- D8 Code Coverage — 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. Coverage NOT MEASURED: test source is present (.kt) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — 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. Test source is present (.kt) and this repository declares a JVM test suite (MiracastReceiver, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — 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. Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 24 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 package.json, but the licence verdict published here was taken over its JVM 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.
- 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 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — 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. `MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/NowPlayingInfo.kt`, `MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/castplus/CastPlusReceiver.kt` 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.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 67 commits in the last 90 days, yet 48 of 72 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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. Boot via AndroidApp (MiracastReceiver/app). the Android app did not build — `./gradlew :app:assembleDebug` exited 1: FAILURE: Build failed with an exception. * What went wrong: Value 'C:\Program Files\Java\jdk-17' given for org.gradle.java.home Gradle property is invalid (Java home supplied is invalid) * Try: > Ru…; runtime evidence skipped (launch chosen because MiracastReceiver/app/build.gradle.kts applies the Android application plugin and MiracastReceiver/gradlew builds it).
- 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.
- 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, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Kotlin, c, cpp 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, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Kotlin, c, cpp 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.
- X24 Document value interpolated into markup unescaped — 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, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
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.
- D13 REDACTED Scanning: REDACTED 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.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- 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.
- 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- 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.
- 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.
- 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
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CastSession.handle at 47. A further 2 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 RtspHandler.routeRequest at 20 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with CastSession.handle (cyclomatic 47). — Refactoring it lifts Cyclomatic Complexity from 7.6 to about 8.1/10.
D2 · Cognitive Complexity
30 method(s) exceeded the cognitive complexity threshold of 15; the worst was CastSession.handle at 64.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cognitive Complexity — start with CastSession.handle (cognitive 64), VideoDecoder.parseSpsResolution (cognitive 39). — 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 2 together lifts Cognitive Complexity from 5.9 to about 7.0/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 4 TooManyMethods finding(s) in God Classes — start with PlayerActivity.kt, RtspHandler.kt, UxPlayReceiver.kt. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with PlayerActivity.kt, CastReceiverService.kt, UpnpHttpServer.kt. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with PlayerActivity.kt, RtspHandler.kt. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. 1.9 % of the production lines (322 of 17,384) are in a reported copy. A further 11 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with AudioStreamServer.kt, AudioPlayer.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (2 corresponding lines) finding(s) in Code Duplication — start with NowPlayingInfo.kt, DlnaMediaRenderer.kt. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with AudioStreamServer.kt, RtspHandler.kt. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
7 production modules (Gradle+npm+CMake), 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; 0 module(s) off the main sequence, with abstractness counted on 1 of the 7 (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).
D6 · Cohesion (LCOM4)
0 of 60 classes have LCOM4 above 3.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 11 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 2 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 13 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, 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
No churn × complexity hotspots in the window.
D16 · Bus Factor
7 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AudioPlayer.kt. Counted over 72 of the 104 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
0 deducted task-comment markers across 17384 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 3 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Gradle, checkout) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
47 % of calls cross a namespace and 0 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
18 finding(s): 0 critical, 17 high, 1 medium, 0 low. semgrep hit a parse error in 3 file(s) — `.github/ISSUE_TEMPLATE/bug_report.yml`, `MiracastReceiver/app/src/main/cpp/alac/ag_dec.c` (line 285, line 302, line 341, …), `MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/castplus/CastPlusReceiver.kt` (line 99, line 287, line 288) — 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.
What to do
- Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). — One of this dimension's main actionable groups (16 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D35 · Change Coupling
No strong hidden change-coupling between production files.
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 1 platform declaration(s) and 26 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
AC1 · Text alternatives
AC2 · Forms & labels
AC3 · Page structure
AC5 · ARIA correctness
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `RaopCallbackHandler` declares 20 abstract methods: `onVideoData`, `onAudioFormat`, `onVideoSize`, `onClientVolume`, `onClientVolumeQuery`, `onAudioTeardown`, `onConnectionInit`, `onConnectionDestroy`, `onConnectionReset`, `onDisplayPin`, `onMetadata`, `onCoverArt`, `onProgress`, `onDacpId`, `onMirrorRunning`, `onVideoPlay`, `onVideoScrub`, `onVideoRate`, `onVideoStop`, `onVideoSessionPoll`. Counted over its public functions with no body, once per name; default-bodied functions and properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/bridge/RaopCallbackHandler.kt:3
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
- `MiracastReceiver/app/build.gradle.kts` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — MiracastReceiver/app/build.gradle.kts:96
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
X23 · Unguarded diagnostic materialisation
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `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) — MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/WfdServer.kt:111, MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/discovery/DeviceInfoProvider.kt:26
- `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. — REDACTED:119
- 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. (×2) — MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/renderer/VideoRenderer.kt:246, MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/renderer/VideoRenderer.kt:263
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84.3 | Strong | Solid. |
| Architecture | 79.9 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 64.6 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36.0 | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 48.3 | Weak — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 100.0 | Exemplary | Strongest area. |
| Performance | 100.0 | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC6 Visual & motion safety — No styled element found in the parsed markup — AC6 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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 function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- 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
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the Android app did not build — `./gradlew :app:assembleDebug` exited 1: FAILURE: Build failed with an exception. * What went wrong: Value 'C:\Program Files\Java\jdk-17' given for org.gradle.java.home Gradle property is invalid (Java home supplied is invalid) * Try: > Ru…; runtime evidence skipped (launch chosen because MiracastReceiver/app/build.gradle.kts applies the Android application plugin and MiracastReceiver/gradlew builds it) This is a statement about this run, not a statement about your application: nothing here says the app is inaccessible, only that it was never run.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
- 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.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~1872 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .kt suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 2 Maven/Gradle manifest(s) were read, stating a version for 24 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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: 4 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .kt, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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) — 2 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- 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.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (53 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- 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, Scala, Rust and Java, 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 — no CI workflow found
- P2 Observability — This repository's JVM source (1 module(s), 100 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM 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 `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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.
- 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.
- 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
- 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 — no C# was loaded; this repository's Kotlin was read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Kotlin request outside a suspend function has no caller's cancellation to honour
- 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
- X24 Document value interpolated into markup unescaped — 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
- 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
- X29 Per-element action decided by a fixed element — 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 — 23 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
Serious — 79 finding(s)
- TooManyMethods: PlayerActivity MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:76
- TooManyMethods: RtspHandler MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt:25
- TooManyMethods: UxPlayReceiver MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/UxPlayReceiver.kt:21
- TooManyMethods: AirPlayReceiver MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AirPlayReceiver.kt:50
- ClassTooLong: PlayerActivity MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:76
- ClassTooLong: CastReceiverService MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/service/CastReceiverService.kt:47
- ClassTooLong: UpnpHttpServer MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/UpnpHttpServer.kt:26
- Swallowed exception (caught, then discarded) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/WfdServer.kt:111
- Swallowed exception (caught, then discarded) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/discovery/DeviceInfoProvider.kt:26
- Swallowed exception (caught, then discarded) REDACTED:119
- FileTooLong: ui/PlayerActivity.kt MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt
- FileTooLong: airplay/RtspHandler.kt MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt
- Edited copy of a member (9 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/AudioStreamServer.kt:502
- Edited copy of a member (9 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AudioPlayer.kt:226
- Edited copy of a member (2 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/NowPlayingInfo.kt:98
- Edited copy of a member (2 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/DlnaMediaRenderer.kt:244
- Duplicated block (11 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/AudioStreamServer.kt:393
- Duplicated block (11 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt:744
- Duplicated block (6 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/utils/NetworkUtils.kt:25
- Duplicated block (6 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/TsDemuxer.kt:114
- Duplicated block (5 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt:962
- Duplicated block (5 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:1394
- Swallowed exception (empty catch) MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/renderer/VideoRenderer.kt:246
- Swallowed exception (empty catch) MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/renderer/VideoRenderer.kt:263
- CastSession.handle (cyclomatic 47) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/cast/CastSession.kt:31
- MainActivity.updateStatus (cyclomatic 29) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/MainActivity.kt:268
- UpnpHttpServer.handleAvTransportControl (cyclomatic 28) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/UpnpHttpServer.kt:166
- VideoDecoder.parseSpsResolution (cyclomatic 27) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/VideoDecoder.kt:412
- AirPlayHlsPlayer.play (cyclomatic 24) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AirPlayHlsPlayer.kt:63
- NameSetupServer.handle (cyclomatic 21) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/settings/NameSetupServer.kt:47
- CastPlusReceiver.event (cyclomatic 20) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/castplus/CastPlusReceiver.kt:124
- PlayerActivity.dispatchKeyEvent (cyclomatic 20) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:590
- PlayerActivity.applyRotation (cyclomatic 19) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:1271
- UpnpHttpServer.handleClient (cyclomatic 18) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/UpnpHttpServer.kt:80
- RtpReceiver.start (cyclomatic 18) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/RtpReceiver.kt:83
- PlayerActivity.detectMirrorContent (cyclomatic 17) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:1464
- RtspHandler.handleMirrorSetup (cyclomatic 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt:925
- SdpParser.parse (cyclomatic 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/SdpParser.kt:48
- TsDemuxer.handlePacket (cyclomatic 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/TsDemuxer.kt:67
- CastSession.handle (cognitive 64) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/cast/CastSession.kt:31
- VideoDecoder.parseSpsResolution (cognitive 39) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/VideoDecoder.kt:412
- RtpReceiver.start (cognitive 30) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/RtpReceiver.kt:83
- PlayerActivity.applyRotation (cognitive 29) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:1271
- AirPlayHlsPlayer.play (cognitive 28) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AirPlayHlsPlayer.kt:63
- SdpParser.parse (cognitive 27) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/SdpParser.kt:48
- NameSetupServer.handle (cognitive 27) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/settings/NameSetupServer.kt:47
- RtspHandler.handleMirrorSetup (cognitive 26) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt:925
- PlayerActivity.dispatchKeyEvent (cognitive 25) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:590
- RtpInterleaved.readLoop (cognitive 21) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtpInterleaved.kt:84
- AirPlayVideoConfigParser.containsRandomAccessFrame (cognitive 21) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/AirPlayVideoConfig.kt:102
- UpnpHttpServer.handleAvTransportControl (cognitive 21) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/UpnpHttpServer.kt:166
- PlayerActivity.detectMirrorContent (cognitive 21) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:1464
- MiracastVideoRenderer.onAccessUnit (cognitive 20) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/MiracastVideoRenderer.kt:63
- DecoderSelector.lowLatencyOptions (cognitive 19) MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/renderer/DecoderSelector.kt:89
- TsDemuxer.parsePmt (cognitive 19) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/TsDemuxer.kt:136
- MirrorStreamServer.runReader (cognitive 18) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/MirrorStreamServer.kt:139
- VideoPipeline._loop (cognitive 17) MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/renderer/VideoPipeline.kt:74
- DmapParser.walk (cognitive 17) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/NowPlayingInfo.kt:74
- MirrorStreamServer.runDecoder (cognitive 17) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/MirrorStreamServer.kt:214
- CastMdnsAdvertiser.start (cognitive 17) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/cast/CastMdnsAdvertiser.kt:26
- PesAssembler.onPacket (cognitive 17) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/TsDemuxer.kt:223
- AirPlayHlsPlayer.refresh (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/AirPlayHlsPlayer.kt:277
- RtspHandler.handleSideClient (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/RtspHandler.kt:330
- GoogleCastReceiver.serve (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/cast/GoogleCastReceiver.kt:90
- UpnpHttpServer.handleClient (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/UpnpHttpServer.kt:80
- WfdSessionHandler.handleRequest (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/WfdSessionHandler.kt:122
- WfdVideoCapabilitiesKt.chooseWfdCustomVideoMode (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/WfdVideoCapabilities.kt:30
- PlayerActivity.updateMirrorSurfaceTarget (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:1327
- ReceiverSettingsMenu.show (cognitive 16) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/ReceiverSettingsMenu.kt:32
- REDACTED
- Edited copy of a member (41 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/AudioStreamServer.kt:385
- Edited copy of a member (31 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/SsdpServer.kt:189
- Edited copy of a member (24 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/PlayerActivity.kt:709
- Edited copy of a member (13 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/utils/NetworkUtils.kt:24
- Edited copy of a member (7 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/ui/CastPlusPlayerActivity.kt:169
- Edited copies of one member (3 members, 1+ corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/FairPlay.kt:83
- Edited copy of a member (5 corresponding lines) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/handshake/AlacDecoder.kt:66
- Duplicated block (15 lines × 2) MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/dlna/SsdpServer.kt:205
- No CI pipeline
Minor — 11 finding(s)
- Fat interface: RaopCallbackHandler (20 abstract methods) MiracastReceiver/app/src/main/java/io/github/jqssun/airplay/bridge/RaopCallbackHandler.kt:3
- Off-boarding risk: anonymized user #1
- No ADRs found MiracastReceiver/app/build.gradle.kts:2
- Projects may be oversized for their cohesion MiracastReceiver/app/build.gradle.kts:1
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation MiracastReceiver/app/build.gradle.kts:96
- Duplicated predicate MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/miracast/WfdSessionHandler.kt:250
- Silent fallback default in catch MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/castplus/CastPlusVideoProfile.kt:54
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-aae27035d4e84edf9b619d98c9b198e9/history.json --exit-code 0 --source . | 6 | 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-aae27035d4e84edf9b619d98c9b198e9/tree.json --exit-code 0 --source . | 6 | 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 . | 18 | 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/** . | 0 | 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 2 file(s) — `MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/airplay/NowPlayingInfo.kt`, `MiracastReceiver/app/src/main/java/top/jast/miracastreceiver/castplus/CastPlusReceiver.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 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 |