Executive summary
geocoder-php/Geocoder falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram, and 47 files are no longer known to anyone active in the project. It scores 64.9 out of 100 and is rated Adequate, and all 25 of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 50.3, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 47 files no active contributor knows, worth about 13.6 points. Recording design decisions comes next, worth about 12.4 points. Raising Maturity to 70 would lift the score to about 74.2.
Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version and passing outside input through environment variables would close both risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and the pipeline step that runs a download without checking it needs each download checked against a known checksum first.
The product code is 12,079 lines, about €27,000 to rebuild.
If Maturity rose from 50.3 to 70, the lowest score rated Strong, the score would rise from 64.9 to about 74.2.
New since the last survey: 16 findings
- Code Duplication · Edited copy of a member (30 corresponding lines) src/Provider/LocationIQ/LocationIQ.php
- Code Duplication · Edited copy of a member (24 corresponding lines) src/Provider/GoogleMaps/GoogleMaps.php
- Code Duplication · Edited copy of a member (30 corresponding lines) src/Provider/IP2LocationBinary/IP2LocationBinary.php
- Code Duplication · Edited copy of a member (15 corresponding lines) src/Http/Provider/AbstractHttpProvider.php
- Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) src/Provider/GeoIPs/GeoIPs.php
- Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) src/Provider/GeoPlugin/GeoPlugin.php
- Code Duplication · Edited copy of a member (11 corresponding lines) src/Common/StatefulGeocoder.php
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Plugin/PluginProvider.php
- Code Duplication · Edited copy of a member (9 corresponding lines) src/Plugin/Plugin/CachePlugin.php
- Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) src/Provider/Geonames/Geonames.php
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) src/Provider/BingMaps/BingMaps.php
- Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) src/Common/Dumper/Kml.php
- Code Duplication · Edited copy of a member (11 corresponding lines) src/Provider/MapQuest/MapQuest.php
- Code Duplication · Edited copy of a member (10 corresponding lines) src/Provider/MapTiler/MapTiler.php
- Code Duplication · Edited copy of a member (7 corresponding lines) src/Common/Model/AddressBuilder.php
- Code Duplication · Edited copy of a member (7 corresponding lines) src/Provider/MapQuest/MapQuest.php
Fixed since the last survey: 5 findings
- Code Duplication · Edited copy of a member (16 corresponding lines) src/Provider/LocationIQ/LocationIQ.php
- Code Duplication · Duplicated block (14 lines × 2) src/Provider/Here/Here.php
- Code Duplication · Duplicated block (11 lines × 3) src/Provider/GeoIPs/GeoIPs.php
- Code Duplication · Duplicated block (10 lines × 2) src/Provider/IP2LocationBinary/IP2LocationBinary.php
- Code Duplication · Duplicated block (8 lines × 2) src/Provider/FreeGeoIp/FreeGeoIp.php
Rebuild cost: about €27,000 · Estimate
| Cost to rebuild | €9,100 to €45,000, for 151 to 479 hours of work, about 0.2 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.9 at a score of 65. 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: 12,079 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 Model | 2 Query | 3 Provider | 4 Geocoder | 5 Http.Provider | 6 Plugin | 7 Provider.AlgoliaPlaces | 8 Provider.ArcGISOnline | 9 Provider.AzureMaps | 10 Provider.BingMaps | 11 Provider.Cache | 12 Provider.FreeGeoIp | 13 Provider.GeoIPs | 14 Provider.GeoPlugin | 15 Provider.Geonames | 16 Provider.GoogleMaps | 17 Provider.GoogleMapsPlaces | 18 Provider.GraphHopper | 19 Provider.Here | 20 Provider.HostIp | 21 Provider.IP2Location | 22 Provider.IpInfo | 23 Provider.IpInfoDb | 24 Provider.Ipstack | 25 Provider.LocationIQ | 26 Provider.MapQuest | 27 Provider.MapTiler | 28 Provider.Mapbox | 29 Provider.Mapzen | 30 Provider.MaxMind | 31 Provider.Nominatim | 32 Provider.OpenCage | 33 Provider.Pelias | 34 Provider.Photon | 35 Provider.PickPoint | 36 Provider.TomTom | 37 Provider.Yandex | 38 Plugin.Plugin | 39 Provider.GeocodeEarth | 40 Provider.OpenRouteService |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Model | 3 | |||||||||||||||||||||||||||||||||||||||
| 2 Query | 2 | |||||||||||||||||||||||||||||||||||||||
| 3 Provider | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 4 Geocoder | 5 | 8 | 4 | |||||||||||||||||||||||||||||||||||||
| 5 Http.Provider | 1 | |||||||||||||||||||||||||||||||||||||||
| 6 Plugin | 3 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 7 Provider.AlgoliaPlaces | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 8 Provider.ArcGISOnline | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 9 Provider.AzureMaps | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 10 Provider.BingMaps | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 11 Provider.Cache | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 12 Provider.FreeGeoIp | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 Provider.GeoIPs | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 14 Provider.GeoPlugin | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 15 Provider.Geonames | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 16 Provider.GoogleMaps | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 17 Provider.GoogleMapsPlaces | 2 | 3 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 18 Provider.GraphHopper | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 19 Provider.Here | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 Provider.HostIp | 3 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 Provider.IP2Location | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 Provider.IpInfo | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 23 Provider.IpInfoDb | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 24 Provider.Ipstack | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 Provider.LocationIQ | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 Provider.MapQuest | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 27 Provider.MapTiler | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 28 Provider.Mapbox | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 Provider.Mapzen | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 Provider.MaxMind | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 Provider.Nominatim | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 Provider.OpenCage | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 Provider.Pelias | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 Provider.Photon | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 Provider.PickPoint | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 Provider.TomTom | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 37 Provider.Yandex | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 38 Plugin.Plugin | 1 | 6 | 6 | |||||||||||||||||||||||||||||||||||||
| 39 Provider.GeocodeEarth | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 Provider.OpenRouteService | 2 | 1 | 1 | 1 |
1→4 Model uses Geocoder part of a loop✕
- Connections
- 3 pairs of types, where a type in Model uses a type in Geocoder.
- The types involved
Geocoder.Model.Address→Geocoder.LocationGeocoder.Model.AddressCollection→Geocoder.CollectionGeocoder.Model.AddressCollection→Geocoder.Location
- Direction
- Model uses Geocoder, so a change to Geocoder can break Model, while a change to Model can't break Geocoder.
- 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.
2→1 Query uses Model✕
- Connections
- 2 pairs of types, where a type in Query uses a type in Model.
- The types involved
Geocoder.Query.GeocodeQuery→Geocoder.Model.BoundsGeocoder.Query.ReverseQuery→Geocoder.Model.Coordinates
- Direction
- Query uses Model, so a change to Model can break Query, while a change to Query can't break Model.
- Position
- Below the diagonal: Query uses a module listed above it, which is the healthy direction.
3→2 Provider uses Query✕
- Connections
- 2 pairs of types, where a type in Provider uses a type in Query.
- The types involved
Geocoder.Provider.Provider→Geocoder.Query.GeocodeQueryGeocoder.Provider.Provider→Geocoder.Query.ReverseQuery
- Direction
- Provider uses Query, so a change to Query can break Provider, while a change to Provider can't break Query.
- Position
- Below the diagonal: Provider uses a module listed above it, which is the healthy direction.
3→4 Provider uses Geocoder part of a loop✕
- Connections
- 2 pairs of types, where a type in Provider uses a type in Geocoder.
- The types involved
Geocoder.Provider.AbstractProvider→Geocoder.LocationGeocoder.Provider.Provider→Geocoder.Collection
- Direction
- Provider uses Geocoder, so a change to Geocoder can break Provider, while a change to Provider can't break Geocoder.
- 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.
4→1 Geocoder uses Model✕
- Connections
- 5 pairs of types, where a type in Geocoder uses a type in Model.
- The types involved
Geocoder.Location→Geocoder.Model.AdminLevelCollectionGeocoder.Location→Geocoder.Model.BoundsGeocoder.Location→Geocoder.Model.CoordinatesGeocoder.Location→Geocoder.Model.CountryGeocoder.StatefulGeocoder→Geocoder.Model.Bounds
- Direction
- Geocoder uses Model, so a change to Model can break Geocoder, while a change to Geocoder can't break Model.
- Position
- Below the diagonal: Geocoder uses a module listed above it, which is the healthy direction.
4→2 Geocoder uses Query✕
- Connections
- 8 pairs of types, where a type in Geocoder uses a type in Query.
- The types involved
Geocoder.GeocoderTrait→Geocoder.Query.GeocodeQueryGeocoder.GeocoderTrait→Geocoder.Query.ReverseQueryGeocoder.ProviderAggregator→Geocoder.Query.GeocodeQueryGeocoder.ProviderAggregator→Geocoder.Query.ReverseQueryGeocoder.StatefulGeocoder→Geocoder.Query.GeocodeQueryGeocoder.StatefulGeocoder→Geocoder.Query.ReverseQueryGeocoder.TimedGeocoder→Geocoder.Query.GeocodeQueryGeocoder.TimedGeocoder→Geocoder.Query.ReverseQuery
- Direction
- Geocoder uses Query, so a change to Query can break Geocoder, while a change to Geocoder can't break Query.
- Position
- Below the diagonal: Geocoder uses a module listed above it, which is the healthy direction.
4→3 Geocoder uses Provider✕
- Connections
- 4 pairs of types, where a type in Geocoder uses a type in Provider.
- The types involved
Geocoder.Geocoder→Geocoder.Provider.ProviderGeocoder.ProviderAggregator→Geocoder.Provider.ProviderGeocoder.StatefulGeocoder→Geocoder.Provider.ProviderGeocoder.TimedGeocoder→Geocoder.Provider.Provider
- Direction
- Geocoder uses Provider, so a change to Provider can break Geocoder, while a change to Geocoder can't break Provider.
- Position
- Below the diagonal: Geocoder uses a module listed above it, which is the healthy direction.
5→3 Http.Provider uses Provider✕
- Connections
- 1 pair of types, where a type in Http.Provider uses a type in Provider.
- The types involved
Geocoder.Http.Provider.AbstractHttpProvider→Geocoder.Provider.AbstractProvider
- Direction
- Http.Provider uses Provider, so a change to Provider can break Http.Provider, while a change to Http.Provider can't break Provider.
- Position
- Below the diagonal: Http.Provider uses a module listed above it, which is the healthy direction.
6→2 Plugin uses Query✕
- Connections
- 3 pairs of types, where a type in Plugin uses a type in Query.
- The types involved
Geocoder.Plugin.Plugin→Geocoder.Query.QueryGeocoder.Plugin.PluginProvider→Geocoder.Query.GeocodeQueryGeocoder.Plugin.PluginProvider→Geocoder.Query.ReverseQuery
- Direction
- Plugin uses Query, so a change to Query can break Plugin, while a change to Plugin can't break Query.
- Position
- Below the diagonal: Plugin uses a module listed above it, which is the healthy direction.
6→3 Plugin uses Provider✕
- Connections
- 1 pair of types, where a type in Plugin uses a type in Provider.
- The types involved
Geocoder.Plugin.PluginProvider→Geocoder.Provider.Provider
- Direction
- Plugin uses Provider, so a change to Provider can break Plugin, while a change to Plugin can't break Provider.
- Position
- Below the diagonal: Plugin uses a module listed above it, which is the healthy direction.
6→4 Plugin uses Geocoder✕
- Connections
- 1 pair of types, where a type in Plugin uses a type in Geocoder.
- The types involved
Geocoder.Plugin.PluginProvider→Geocoder.Collection
- Direction
- Plugin uses Geocoder, so a change to Geocoder can break Plugin, while a change to Plugin can't break Geocoder.
- Position
- Below the diagonal: Plugin uses a module listed above it, which is the healthy direction.
7→1 Provider.AlgoliaPlaces uses Model✕
- Connections
- 1 pair of types, where a type in Provider.AlgoliaPlaces uses a type in Model.
- The types involved
Geocoder.Provider.AlgoliaPlaces.AlgoliaPlaces→Geocoder.Model.AddressCollection
- Direction
- Provider.AlgoliaPlaces uses Model, so a change to Model can break Provider.AlgoliaPlaces, while a change to Provider.AlgoliaPlaces can't break Model.
- Position
- Below the diagonal: Provider.AlgoliaPlaces uses a module listed above it, which is the healthy direction.
7→2 Provider.AlgoliaPlaces uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.AlgoliaPlaces uses a type in Query.
- The types involved
Geocoder.Provider.AlgoliaPlaces.AlgoliaPlaces→Geocoder.Query.GeocodeQueryGeocoder.Provider.AlgoliaPlaces.AlgoliaPlaces→Geocoder.Query.ReverseQuery
- Direction
- Provider.AlgoliaPlaces uses Query, so a change to Query can break Provider.AlgoliaPlaces, while a change to Provider.AlgoliaPlaces can't break Query.
- Position
- Below the diagonal: Provider.AlgoliaPlaces uses a module listed above it, which is the healthy direction.
7→3 Provider.AlgoliaPlaces uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.AlgoliaPlaces uses a type in Provider.
- The types involved
Geocoder.Provider.AlgoliaPlaces.AlgoliaPlaces→Geocoder.Provider.Provider
- Direction
- Provider.AlgoliaPlaces uses Provider, so a change to Provider can break Provider.AlgoliaPlaces, while a change to Provider.AlgoliaPlaces can't break Provider.
- Position
- Below the diagonal: Provider.AlgoliaPlaces uses a module listed above it, which is the healthy direction.
7→4 Provider.AlgoliaPlaces uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.AlgoliaPlaces uses a type in Geocoder.
- The types involved
Geocoder.Provider.AlgoliaPlaces.AlgoliaPlaces→Geocoder.Collection
- Direction
- Provider.AlgoliaPlaces uses Geocoder, so a change to Geocoder can break Provider.AlgoliaPlaces, while a change to Provider.AlgoliaPlaces can't break Geocoder.
- Position
- Below the diagonal: Provider.AlgoliaPlaces uses a module listed above it, which is the healthy direction.
7→5 Provider.AlgoliaPlaces uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.AlgoliaPlaces uses a type in Http.Provider.
- The types involved
Geocoder.Provider.AlgoliaPlaces.AlgoliaPlaces→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.AlgoliaPlaces uses Http.Provider, so a change to Http.Provider can break Provider.AlgoliaPlaces, while a change to Provider.AlgoliaPlaces can't break Http.Provider.
- Position
- Below the diagonal: Provider.AlgoliaPlaces uses a module listed above it, which is the healthy direction.
8→2 Provider.ArcGISOnline uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.ArcGISOnline uses a type in Query.
- The types involved
Geocoder.Provider.ArcGISOnline.ArcGISOnline→Geocoder.Query.GeocodeQueryGeocoder.Provider.ArcGISOnline.ArcGISOnline→Geocoder.Query.ReverseQuery
- Direction
- Provider.ArcGISOnline uses Query, so a change to Query can break Provider.ArcGISOnline, while a change to Provider.ArcGISOnline can't break Query.
- Position
- Below the diagonal: Provider.ArcGISOnline uses a module listed above it, which is the healthy direction.
8→3 Provider.ArcGISOnline uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.ArcGISOnline uses a type in Provider.
- The types involved
Geocoder.Provider.ArcGISOnline.ArcGISOnline→Geocoder.Provider.Provider
- Direction
- Provider.ArcGISOnline uses Provider, so a change to Provider can break Provider.ArcGISOnline, while a change to Provider.ArcGISOnline can't break Provider.
- Position
- Below the diagonal: Provider.ArcGISOnline uses a module listed above it, which is the healthy direction.
8→4 Provider.ArcGISOnline uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.ArcGISOnline uses a type in Geocoder.
- The types involved
Geocoder.Provider.ArcGISOnline.ArcGISOnline→Geocoder.Collection
- Direction
- Provider.ArcGISOnline uses Geocoder, so a change to Geocoder can break Provider.ArcGISOnline, while a change to Provider.ArcGISOnline can't break Geocoder.
- Position
- Below the diagonal: Provider.ArcGISOnline uses a module listed above it, which is the healthy direction.
8→5 Provider.ArcGISOnline uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.ArcGISOnline uses a type in Http.Provider.
- The types involved
Geocoder.Provider.ArcGISOnline.ArcGISOnline→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.ArcGISOnline uses Http.Provider, so a change to Http.Provider can break Provider.ArcGISOnline, while a change to Provider.ArcGISOnline can't break Http.Provider.
- Position
- Below the diagonal: Provider.ArcGISOnline uses a module listed above it, which is the healthy direction.
9→2 Provider.AzureMaps uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.AzureMaps uses a type in Query.
- The types involved
Geocoder.Provider.AzureMaps.AzureMaps→Geocoder.Query.GeocodeQueryGeocoder.Provider.AzureMaps.AzureMaps→Geocoder.Query.ReverseQuery
- Direction
- Provider.AzureMaps uses Query, so a change to Query can break Provider.AzureMaps, while a change to Provider.AzureMaps can't break Query.
- Position
- Below the diagonal: Provider.AzureMaps uses a module listed above it, which is the healthy direction.
9→3 Provider.AzureMaps uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.AzureMaps uses a type in Provider.
- The types involved
Geocoder.Provider.AzureMaps.AzureMaps→Geocoder.Provider.Provider
- Direction
- Provider.AzureMaps uses Provider, so a change to Provider can break Provider.AzureMaps, while a change to Provider.AzureMaps can't break Provider.
- Position
- Below the diagonal: Provider.AzureMaps uses a module listed above it, which is the healthy direction.
9→4 Provider.AzureMaps uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.AzureMaps uses a type in Geocoder.
- The types involved
Geocoder.Provider.AzureMaps.AzureMaps→Geocoder.Collection
- Direction
- Provider.AzureMaps uses Geocoder, so a change to Geocoder can break Provider.AzureMaps, while a change to Provider.AzureMaps can't break Geocoder.
- Position
- Below the diagonal: Provider.AzureMaps uses a module listed above it, which is the healthy direction.
9→5 Provider.AzureMaps uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.AzureMaps uses a type in Http.Provider.
- The types involved
Geocoder.Provider.AzureMaps.AzureMaps→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.AzureMaps uses Http.Provider, so a change to Http.Provider can break Provider.AzureMaps, while a change to Provider.AzureMaps can't break Http.Provider.
- Position
- Below the diagonal: Provider.AzureMaps uses a module listed above it, which is the healthy direction.
10→2 Provider.BingMaps uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.BingMaps uses a type in Query.
- The types involved
Geocoder.Provider.BingMaps.BingMaps→Geocoder.Query.GeocodeQueryGeocoder.Provider.BingMaps.BingMaps→Geocoder.Query.ReverseQuery
- Direction
- Provider.BingMaps uses Query, so a change to Query can break Provider.BingMaps, while a change to Provider.BingMaps can't break Query.
- Position
- Below the diagonal: Provider.BingMaps uses a module listed above it, which is the healthy direction.
10→3 Provider.BingMaps uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.BingMaps uses a type in Provider.
- The types involved
Geocoder.Provider.BingMaps.BingMaps→Geocoder.Provider.Provider
- Direction
- Provider.BingMaps uses Provider, so a change to Provider can break Provider.BingMaps, while a change to Provider.BingMaps can't break Provider.
- Position
- Below the diagonal: Provider.BingMaps uses a module listed above it, which is the healthy direction.
10→4 Provider.BingMaps uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.BingMaps uses a type in Geocoder.
- The types involved
Geocoder.Provider.BingMaps.BingMaps→Geocoder.Collection
- Direction
- Provider.BingMaps uses Geocoder, so a change to Geocoder can break Provider.BingMaps, while a change to Provider.BingMaps can't break Geocoder.
- Position
- Below the diagonal: Provider.BingMaps uses a module listed above it, which is the healthy direction.
10→5 Provider.BingMaps uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.BingMaps uses a type in Http.Provider.
- The types involved
Geocoder.Provider.BingMaps.BingMaps→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.BingMaps uses Http.Provider, so a change to Http.Provider can break Provider.BingMaps, while a change to Provider.BingMaps can't break Http.Provider.
- Position
- Below the diagonal: Provider.BingMaps uses a module listed above it, which is the healthy direction.
11→2 Provider.Cache uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Cache uses a type in Query.
- The types involved
Geocoder.Provider.Cache.ProviderCache→Geocoder.Query.GeocodeQueryGeocoder.Provider.Cache.ProviderCache→Geocoder.Query.ReverseQuery
- Direction
- Provider.Cache uses Query, so a change to Query can break Provider.Cache, while a change to Provider.Cache can't break Query.
- Position
- Below the diagonal: Provider.Cache uses a module listed above it, which is the healthy direction.
11→3 Provider.Cache uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Cache uses a type in Provider.
- The types involved
Geocoder.Provider.Cache.ProviderCache→Geocoder.Provider.Provider
- Direction
- Provider.Cache uses Provider, so a change to Provider can break Provider.Cache, while a change to Provider.Cache can't break Provider.
- Position
- Below the diagonal: Provider.Cache uses a module listed above it, which is the healthy direction.
11→4 Provider.Cache uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Cache uses a type in Geocoder.
- The types involved
Geocoder.Provider.Cache.ProviderCache→Geocoder.Collection
- Direction
- Provider.Cache uses Geocoder, so a change to Geocoder can break Provider.Cache, while a change to Provider.Cache can't break Geocoder.
- Position
- Below the diagonal: Provider.Cache uses a module listed above it, which is the healthy direction.
12→2 Provider.FreeGeoIp uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.FreeGeoIp uses a type in Query.
- The types involved
Geocoder.Provider.FreeGeoIp.FreeGeoIp→Geocoder.Query.GeocodeQueryGeocoder.Provider.FreeGeoIp.FreeGeoIp→Geocoder.Query.ReverseQuery
- Direction
- Provider.FreeGeoIp uses Query, so a change to Query can break Provider.FreeGeoIp, while a change to Provider.FreeGeoIp can't break Query.
- Position
- Below the diagonal: Provider.FreeGeoIp uses a module listed above it, which is the healthy direction.
12→3 Provider.FreeGeoIp uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.FreeGeoIp uses a type in Provider.
- The types involved
Geocoder.Provider.FreeGeoIp.FreeGeoIp→Geocoder.Provider.Provider
- Direction
- Provider.FreeGeoIp uses Provider, so a change to Provider can break Provider.FreeGeoIp, while a change to Provider.FreeGeoIp can't break Provider.
- Position
- Below the diagonal: Provider.FreeGeoIp uses a module listed above it, which is the healthy direction.
12→4 Provider.FreeGeoIp uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.FreeGeoIp uses a type in Geocoder.
- The types involved
Geocoder.Provider.FreeGeoIp.FreeGeoIp→Geocoder.Collection
- Direction
- Provider.FreeGeoIp uses Geocoder, so a change to Geocoder can break Provider.FreeGeoIp, while a change to Provider.FreeGeoIp can't break Geocoder.
- Position
- Below the diagonal: Provider.FreeGeoIp uses a module listed above it, which is the healthy direction.
12→5 Provider.FreeGeoIp uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.FreeGeoIp uses a type in Http.Provider.
- The types involved
Geocoder.Provider.FreeGeoIp.FreeGeoIp→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.FreeGeoIp uses Http.Provider, so a change to Http.Provider can break Provider.FreeGeoIp, while a change to Provider.FreeGeoIp can't break Http.Provider.
- Position
- Below the diagonal: Provider.FreeGeoIp uses a module listed above it, which is the healthy direction.
13→1 Provider.GeoIPs uses Model✕
- Connections
- 1 pair of types, where a type in Provider.GeoIPs uses a type in Model.
- The types involved
Geocoder.Provider.GeoIPs.GeoIPs→Geocoder.Model.AddressCollection
- Direction
- Provider.GeoIPs uses Model, so a change to Model can break Provider.GeoIPs, while a change to Provider.GeoIPs can't break Model.
- Position
- Below the diagonal: Provider.GeoIPs uses a module listed above it, which is the healthy direction.
13→2 Provider.GeoIPs uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.GeoIPs uses a type in Query.
- The types involved
Geocoder.Provider.GeoIPs.GeoIPs→Geocoder.Query.GeocodeQueryGeocoder.Provider.GeoIPs.GeoIPs→Geocoder.Query.ReverseQuery
- Direction
- Provider.GeoIPs uses Query, so a change to Query can break Provider.GeoIPs, while a change to Provider.GeoIPs can't break Query.
- Position
- Below the diagonal: Provider.GeoIPs uses a module listed above it, which is the healthy direction.
13→3 Provider.GeoIPs uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.GeoIPs uses a type in Provider.
- The types involved
Geocoder.Provider.GeoIPs.GeoIPs→Geocoder.Provider.Provider
- Direction
- Provider.GeoIPs uses Provider, so a change to Provider can break Provider.GeoIPs, while a change to Provider.GeoIPs can't break Provider.
- Position
- Below the diagonal: Provider.GeoIPs uses a module listed above it, which is the healthy direction.
13→4 Provider.GeoIPs uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.GeoIPs uses a type in Geocoder.
- The types involved
Geocoder.Provider.GeoIPs.GeoIPs→Geocoder.Collection
- Direction
- Provider.GeoIPs uses Geocoder, so a change to Geocoder can break Provider.GeoIPs, while a change to Provider.GeoIPs can't break Geocoder.
- Position
- Below the diagonal: Provider.GeoIPs uses a module listed above it, which is the healthy direction.
13→5 Provider.GeoIPs uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.GeoIPs uses a type in Http.Provider.
- The types involved
Geocoder.Provider.GeoIPs.GeoIPs→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.GeoIPs uses Http.Provider, so a change to Http.Provider can break Provider.GeoIPs, while a change to Provider.GeoIPs can't break Http.Provider.
- Position
- Below the diagonal: Provider.GeoIPs uses a module listed above it, which is the healthy direction.
14→1 Provider.GeoPlugin uses Model✕
- Connections
- 1 pair of types, where a type in Provider.GeoPlugin uses a type in Model.
- The types involved
Geocoder.Provider.GeoPlugin.GeoPlugin→Geocoder.Model.AddressCollection
- Direction
- Provider.GeoPlugin uses Model, so a change to Model can break Provider.GeoPlugin, while a change to Provider.GeoPlugin can't break Model.
- Position
- Below the diagonal: Provider.GeoPlugin uses a module listed above it, which is the healthy direction.
14→2 Provider.GeoPlugin uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.GeoPlugin uses a type in Query.
- The types involved
Geocoder.Provider.GeoPlugin.GeoPlugin→Geocoder.Query.GeocodeQueryGeocoder.Provider.GeoPlugin.GeoPlugin→Geocoder.Query.ReverseQuery
- Direction
- Provider.GeoPlugin uses Query, so a change to Query can break Provider.GeoPlugin, while a change to Provider.GeoPlugin can't break Query.
- Position
- Below the diagonal: Provider.GeoPlugin uses a module listed above it, which is the healthy direction.
14→3 Provider.GeoPlugin uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.GeoPlugin uses a type in Provider.
- The types involved
Geocoder.Provider.GeoPlugin.GeoPlugin→Geocoder.Provider.Provider
- Direction
- Provider.GeoPlugin uses Provider, so a change to Provider can break Provider.GeoPlugin, while a change to Provider.GeoPlugin can't break Provider.
- Position
- Below the diagonal: Provider.GeoPlugin uses a module listed above it, which is the healthy direction.
14→4 Provider.GeoPlugin uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.GeoPlugin uses a type in Geocoder.
- The types involved
Geocoder.Provider.GeoPlugin.GeoPlugin→Geocoder.Collection
- Direction
- Provider.GeoPlugin uses Geocoder, so a change to Geocoder can break Provider.GeoPlugin, while a change to Provider.GeoPlugin can't break Geocoder.
- Position
- Below the diagonal: Provider.GeoPlugin uses a module listed above it, which is the healthy direction.
14→5 Provider.GeoPlugin uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.GeoPlugin uses a type in Http.Provider.
- The types involved
Geocoder.Provider.GeoPlugin.GeoPlugin→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.GeoPlugin uses Http.Provider, so a change to Http.Provider can break Provider.GeoPlugin, while a change to Provider.GeoPlugin can't break Http.Provider.
- Position
- Below the diagonal: Provider.GeoPlugin uses a module listed above it, which is the healthy direction.
15→1 Provider.Geonames uses Model✕
- Connections
- 1 pair of types, where a type in Provider.Geonames uses a type in Model.
- The types involved
Geocoder.Provider.Geonames.Geonames→Geocoder.Model.AddressCollection
- Direction
- Provider.Geonames uses Model, so a change to Model can break Provider.Geonames, while a change to Provider.Geonames can't break Model.
- Position
- Below the diagonal: Provider.Geonames uses a module listed above it, which is the healthy direction.
15→2 Provider.Geonames uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Geonames uses a type in Query.
- The types involved
Geocoder.Provider.Geonames.Geonames→Geocoder.Query.GeocodeQueryGeocoder.Provider.Geonames.Geonames→Geocoder.Query.ReverseQuery
- Direction
- Provider.Geonames uses Query, so a change to Query can break Provider.Geonames, while a change to Provider.Geonames can't break Query.
- Position
- Below the diagonal: Provider.Geonames uses a module listed above it, which is the healthy direction.
15→3 Provider.Geonames uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Geonames uses a type in Provider.
- The types involved
Geocoder.Provider.Geonames.Geonames→Geocoder.Provider.Provider
- Direction
- Provider.Geonames uses Provider, so a change to Provider can break Provider.Geonames, while a change to Provider.Geonames can't break Provider.
- Position
- Below the diagonal: Provider.Geonames uses a module listed above it, which is the healthy direction.
15→4 Provider.Geonames uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Geonames uses a type in Geocoder.
- The types involved
Geocoder.Provider.Geonames.Geonames→Geocoder.Collection
- Direction
- Provider.Geonames uses Geocoder, so a change to Geocoder can break Provider.Geonames, while a change to Provider.Geonames can't break Geocoder.
- Position
- Below the diagonal: Provider.Geonames uses a module listed above it, which is the healthy direction.
15→5 Provider.Geonames uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Geonames uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Geonames.Geonames→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Geonames uses Http.Provider, so a change to Http.Provider can break Provider.Geonames, while a change to Provider.Geonames can't break Http.Provider.
- Position
- Below the diagonal: Provider.Geonames uses a module listed above it, which is the healthy direction.
16→1 Provider.GoogleMaps uses Model✕
- Connections
- 2 pairs of types, where a type in Provider.GoogleMaps uses a type in Model.
- The types involved
Geocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Model.AddressBuilderGeocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Model.AddressCollection
- Direction
- Provider.GoogleMaps uses Model, so a change to Model can break Provider.GoogleMaps, while a change to Provider.GoogleMaps can't break Model.
- Position
- Below the diagonal: Provider.GoogleMaps uses a module listed above it, which is the healthy direction.
16→2 Provider.GoogleMaps uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.GoogleMaps uses a type in Query.
- The types involved
Geocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Query.GeocodeQueryGeocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Query.ReverseQuery
- Direction
- Provider.GoogleMaps uses Query, so a change to Query can break Provider.GoogleMaps, while a change to Provider.GoogleMaps can't break Query.
- Position
- Below the diagonal: Provider.GoogleMaps uses a module listed above it, which is the healthy direction.
16→3 Provider.GoogleMaps uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.GoogleMaps uses a type in Provider.
- The types involved
Geocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Provider.Provider
- Direction
- Provider.GoogleMaps uses Provider, so a change to Provider can break Provider.GoogleMaps, while a change to Provider.GoogleMaps can't break Provider.
- Position
- Below the diagonal: Provider.GoogleMaps uses a module listed above it, which is the healthy direction.
16→4 Provider.GoogleMaps uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.GoogleMaps uses a type in Geocoder.
- The types involved
Geocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Collection
- Direction
- Provider.GoogleMaps uses Geocoder, so a change to Geocoder can break Provider.GoogleMaps, while a change to Provider.GoogleMaps can't break Geocoder.
- Position
- Below the diagonal: Provider.GoogleMaps uses a module listed above it, which is the healthy direction.
16→5 Provider.GoogleMaps uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.GoogleMaps uses a type in Http.Provider.
- The types involved
Geocoder.Provider.GoogleMaps.GoogleMaps→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.GoogleMaps uses Http.Provider, so a change to Http.Provider can break Provider.GoogleMaps, while a change to Provider.GoogleMaps can't break Http.Provider.
- Position
- Below the diagonal: Provider.GoogleMaps uses a module listed above it, which is the healthy direction.
17→1 Provider.GoogleMapsPlaces uses Model✕
- Connections
- 2 pairs of types, where a type in Provider.GoogleMapsPlaces uses a type in Model.
- The types involved
Geocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Model.AddressBuilderGeocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Model.AddressCollection
- Direction
- Provider.GoogleMapsPlaces uses Model, so a change to Model can break Provider.GoogleMapsPlaces, while a change to Provider.GoogleMapsPlaces can't break Model.
- Position
- Below the diagonal: Provider.GoogleMapsPlaces uses a module listed above it, which is the healthy direction.
17→2 Provider.GoogleMapsPlaces uses Query✕
- Connections
- 3 pairs of types, where a type in Provider.GoogleMapsPlaces uses a type in Query.
- The types involved
Geocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Query.GeocodeQueryGeocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Query.QueryGeocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Query.ReverseQuery
- Direction
- Provider.GoogleMapsPlaces uses Query, so a change to Query can break Provider.GoogleMapsPlaces, while a change to Provider.GoogleMapsPlaces can't break Query.
- Position
- Below the diagonal: Provider.GoogleMapsPlaces uses a module listed above it, which is the healthy direction.
17→3 Provider.GoogleMapsPlaces uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.GoogleMapsPlaces uses a type in Provider.
- The types involved
Geocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Provider.Provider
- Direction
- Provider.GoogleMapsPlaces uses Provider, so a change to Provider can break Provider.GoogleMapsPlaces, while a change to Provider.GoogleMapsPlaces can't break Provider.
- Position
- Below the diagonal: Provider.GoogleMapsPlaces uses a module listed above it, which is the healthy direction.
17→4 Provider.GoogleMapsPlaces uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.GoogleMapsPlaces uses a type in Geocoder.
- The types involved
Geocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Collection
- Direction
- Provider.GoogleMapsPlaces uses Geocoder, so a change to Geocoder can break Provider.GoogleMapsPlaces, while a change to Provider.GoogleMapsPlaces can't break Geocoder.
- Position
- Below the diagonal: Provider.GoogleMapsPlaces uses a module listed above it, which is the healthy direction.
17→5 Provider.GoogleMapsPlaces uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.GoogleMapsPlaces uses a type in Http.Provider.
- The types involved
Geocoder.Provider.GoogleMapsPlaces.GoogleMapsPlaces→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.GoogleMapsPlaces uses Http.Provider, so a change to Http.Provider can break Provider.GoogleMapsPlaces, while a change to Provider.GoogleMapsPlaces can't break Http.Provider.
- Position
- Below the diagonal: Provider.GoogleMapsPlaces uses a module listed above it, which is the healthy direction.
18→1 Provider.GraphHopper uses Model✕
- Connections
- 1 pair of types, where a type in Provider.GraphHopper uses a type in Model.
- The types involved
Geocoder.Provider.GraphHopper.GraphHopper→Geocoder.Model.AddressCollection
- Direction
- Provider.GraphHopper uses Model, so a change to Model can break Provider.GraphHopper, while a change to Provider.GraphHopper can't break Model.
- Position
- Below the diagonal: Provider.GraphHopper uses a module listed above it, which is the healthy direction.
18→2 Provider.GraphHopper uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.GraphHopper uses a type in Query.
- The types involved
Geocoder.Provider.GraphHopper.GraphHopper→Geocoder.Query.GeocodeQueryGeocoder.Provider.GraphHopper.GraphHopper→Geocoder.Query.ReverseQuery
- Direction
- Provider.GraphHopper uses Query, so a change to Query can break Provider.GraphHopper, while a change to Provider.GraphHopper can't break Query.
- Position
- Below the diagonal: Provider.GraphHopper uses a module listed above it, which is the healthy direction.
18→3 Provider.GraphHopper uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.GraphHopper uses a type in Provider.
- The types involved
Geocoder.Provider.GraphHopper.GraphHopper→Geocoder.Provider.Provider
- Direction
- Provider.GraphHopper uses Provider, so a change to Provider can break Provider.GraphHopper, while a change to Provider.GraphHopper can't break Provider.
- Position
- Below the diagonal: Provider.GraphHopper uses a module listed above it, which is the healthy direction.
18→4 Provider.GraphHopper uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.GraphHopper uses a type in Geocoder.
- The types involved
Geocoder.Provider.GraphHopper.GraphHopper→Geocoder.Collection
- Direction
- Provider.GraphHopper uses Geocoder, so a change to Geocoder can break Provider.GraphHopper, while a change to Provider.GraphHopper can't break Geocoder.
- Position
- Below the diagonal: Provider.GraphHopper uses a module listed above it, which is the healthy direction.
18→5 Provider.GraphHopper uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.GraphHopper uses a type in Http.Provider.
- The types involved
Geocoder.Provider.GraphHopper.GraphHopper→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.GraphHopper uses Http.Provider, so a change to Http.Provider can break Provider.GraphHopper, while a change to Provider.GraphHopper can't break Http.Provider.
- Position
- Below the diagonal: Provider.GraphHopper uses a module listed above it, which is the healthy direction.
19→2 Provider.Here uses Query✕
- Connections
- 3 pairs of types, where a type in Provider.Here uses a type in Query.
- The types involved
Geocoder.Provider.Here.Here→Geocoder.Query.GeocodeQueryGeocoder.Provider.Here.Here→Geocoder.Query.QueryGeocoder.Provider.Here.Here→Geocoder.Query.ReverseQuery
- Direction
- Provider.Here uses Query, so a change to Query can break Provider.Here, while a change to Provider.Here can't break Query.
- Position
- Below the diagonal: Provider.Here uses a module listed above it, which is the healthy direction.
19→3 Provider.Here uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Here uses a type in Provider.
- The types involved
Geocoder.Provider.Here.Here→Geocoder.Provider.Provider
- Direction
- Provider.Here uses Provider, so a change to Provider can break Provider.Here, while a change to Provider.Here can't break Provider.
- Position
- Below the diagonal: Provider.Here uses a module listed above it, which is the healthy direction.
19→4 Provider.Here uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Here uses a type in Geocoder.
- The types involved
Geocoder.Provider.Here.Here→Geocoder.Collection
- Direction
- Provider.Here uses Geocoder, so a change to Geocoder can break Provider.Here, while a change to Provider.Here can't break Geocoder.
- Position
- Below the diagonal: Provider.Here uses a module listed above it, which is the healthy direction.
19→5 Provider.Here uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Here uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Here.Here→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Here uses Http.Provider, so a change to Http.Provider can break Provider.Here, while a change to Provider.Here can't break Http.Provider.
- Position
- Below the diagonal: Provider.Here uses a module listed above it, which is the healthy direction.
20→1 Provider.HostIp uses Model✕
- Connections
- 3 pairs of types, where a type in Provider.HostIp uses a type in Model.
- The types involved
Geocoder.Provider.HostIp.AbstractHostIp→Geocoder.Model.AddressCollectionGeocoder.Provider.HostIp.HostIp→Geocoder.Model.AddressCollectionGeocoder.Provider.HostIp.HostIpXml→Geocoder.Model.AddressCollection
- Direction
- Provider.HostIp uses Model, so a change to Model can break Provider.HostIp, while a change to Provider.HostIp can't break Model.
- Position
- Below the diagonal: Provider.HostIp uses a module listed above it, which is the healthy direction.
20→2 Provider.HostIp uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.HostIp uses a type in Query.
- The types involved
Geocoder.Provider.HostIp.AbstractHostIp→Geocoder.Query.GeocodeQueryGeocoder.Provider.HostIp.AbstractHostIp→Geocoder.Query.ReverseQuery
- Direction
- Provider.HostIp uses Query, so a change to Query can break Provider.HostIp, while a change to Provider.HostIp can't break Query.
- Position
- Below the diagonal: Provider.HostIp uses a module listed above it, which is the healthy direction.
20→3 Provider.HostIp uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.HostIp uses a type in Provider.
- The types involved
Geocoder.Provider.HostIp.AbstractHostIp→Geocoder.Provider.Provider
- Direction
- Provider.HostIp uses Provider, so a change to Provider can break Provider.HostIp, while a change to Provider.HostIp can't break Provider.
- Position
- Below the diagonal: Provider.HostIp uses a module listed above it, which is the healthy direction.
20→4 Provider.HostIp uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.HostIp uses a type in Geocoder.
- The types involved
Geocoder.Provider.HostIp.AbstractHostIp→Geocoder.Collection
- Direction
- Provider.HostIp uses Geocoder, so a change to Geocoder can break Provider.HostIp, while a change to Provider.HostIp can't break Geocoder.
- Position
- Below the diagonal: Provider.HostIp uses a module listed above it, which is the healthy direction.
20→5 Provider.HostIp uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.HostIp uses a type in Http.Provider.
- The types involved
Geocoder.Provider.HostIp.AbstractHostIp→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.HostIp uses Http.Provider, so a change to Http.Provider can break Provider.HostIp, while a change to Provider.HostIp can't break Http.Provider.
- Position
- Below the diagonal: Provider.HostIp uses a module listed above it, which is the healthy direction.
21→1 Provider.IP2Location uses Model✕
- Connections
- 1 pair of types, where a type in Provider.IP2Location uses a type in Model.
- The types involved
Geocoder.Provider.IP2Location.IP2Location→Geocoder.Model.AddressCollection
- Direction
- Provider.IP2Location uses Model, so a change to Model can break Provider.IP2Location, while a change to Provider.IP2Location can't break Model.
- Position
- Below the diagonal: Provider.IP2Location uses a module listed above it, which is the healthy direction.
21→2 Provider.IP2Location uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.IP2Location uses a type in Query.
- The types involved
Geocoder.Provider.IP2Location.IP2Location→Geocoder.Query.GeocodeQueryGeocoder.Provider.IP2Location.IP2Location→Geocoder.Query.ReverseQuery
- Direction
- Provider.IP2Location uses Query, so a change to Query can break Provider.IP2Location, while a change to Provider.IP2Location can't break Query.
- Position
- Below the diagonal: Provider.IP2Location uses a module listed above it, which is the healthy direction.
21→3 Provider.IP2Location uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.IP2Location uses a type in Provider.
- The types involved
Geocoder.Provider.IP2Location.IP2Location→Geocoder.Provider.Provider
- Direction
- Provider.IP2Location uses Provider, so a change to Provider can break Provider.IP2Location, while a change to Provider.IP2Location can't break Provider.
- Position
- Below the diagonal: Provider.IP2Location uses a module listed above it, which is the healthy direction.
21→4 Provider.IP2Location uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.IP2Location uses a type in Geocoder.
- The types involved
Geocoder.Provider.IP2Location.IP2Location→Geocoder.Collection
- Direction
- Provider.IP2Location uses Geocoder, so a change to Geocoder can break Provider.IP2Location, while a change to Provider.IP2Location can't break Geocoder.
- Position
- Below the diagonal: Provider.IP2Location uses a module listed above it, which is the healthy direction.
21→5 Provider.IP2Location uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.IP2Location uses a type in Http.Provider.
- The types involved
Geocoder.Provider.IP2Location.IP2Location→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.IP2Location uses Http.Provider, so a change to Http.Provider can break Provider.IP2Location, while a change to Provider.IP2Location can't break Http.Provider.
- Position
- Below the diagonal: Provider.IP2Location uses a module listed above it, which is the healthy direction.
22→1 Provider.IpInfo uses Model✕
- Connections
- 1 pair of types, where a type in Provider.IpInfo uses a type in Model.
- The types involved
Geocoder.Provider.IpInfo.IpInfo→Geocoder.Model.AddressCollection
- Direction
- Provider.IpInfo uses Model, so a change to Model can break Provider.IpInfo, while a change to Provider.IpInfo can't break Model.
- Position
- Below the diagonal: Provider.IpInfo uses a module listed above it, which is the healthy direction.
22→2 Provider.IpInfo uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.IpInfo uses a type in Query.
- The types involved
Geocoder.Provider.IpInfo.IpInfo→Geocoder.Query.GeocodeQueryGeocoder.Provider.IpInfo.IpInfo→Geocoder.Query.ReverseQuery
- Direction
- Provider.IpInfo uses Query, so a change to Query can break Provider.IpInfo, while a change to Provider.IpInfo can't break Query.
- Position
- Below the diagonal: Provider.IpInfo uses a module listed above it, which is the healthy direction.
22→3 Provider.IpInfo uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.IpInfo uses a type in Provider.
- The types involved
Geocoder.Provider.IpInfo.IpInfo→Geocoder.Provider.Provider
- Direction
- Provider.IpInfo uses Provider, so a change to Provider can break Provider.IpInfo, while a change to Provider.IpInfo can't break Provider.
- Position
- Below the diagonal: Provider.IpInfo uses a module listed above it, which is the healthy direction.
22→4 Provider.IpInfo uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.IpInfo uses a type in Geocoder.
- The types involved
Geocoder.Provider.IpInfo.IpInfo→Geocoder.Collection
- Direction
- Provider.IpInfo uses Geocoder, so a change to Geocoder can break Provider.IpInfo, while a change to Provider.IpInfo can't break Geocoder.
- Position
- Below the diagonal: Provider.IpInfo uses a module listed above it, which is the healthy direction.
22→5 Provider.IpInfo uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.IpInfo uses a type in Http.Provider.
- The types involved
Geocoder.Provider.IpInfo.IpInfo→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.IpInfo uses Http.Provider, so a change to Http.Provider can break Provider.IpInfo, while a change to Provider.IpInfo can't break Http.Provider.
- Position
- Below the diagonal: Provider.IpInfo uses a module listed above it, which is the healthy direction.
23→1 Provider.IpInfoDb uses Model✕
- Connections
- 1 pair of types, where a type in Provider.IpInfoDb uses a type in Model.
- The types involved
Geocoder.Provider.IpInfoDb.IpInfoDb→Geocoder.Model.AddressCollection
- Direction
- Provider.IpInfoDb uses Model, so a change to Model can break Provider.IpInfoDb, while a change to Provider.IpInfoDb can't break Model.
- Position
- Below the diagonal: Provider.IpInfoDb uses a module listed above it, which is the healthy direction.
23→2 Provider.IpInfoDb uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.IpInfoDb uses a type in Query.
- The types involved
Geocoder.Provider.IpInfoDb.IpInfoDb→Geocoder.Query.GeocodeQueryGeocoder.Provider.IpInfoDb.IpInfoDb→Geocoder.Query.ReverseQuery
- Direction
- Provider.IpInfoDb uses Query, so a change to Query can break Provider.IpInfoDb, while a change to Provider.IpInfoDb can't break Query.
- Position
- Below the diagonal: Provider.IpInfoDb uses a module listed above it, which is the healthy direction.
23→3 Provider.IpInfoDb uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.IpInfoDb uses a type in Provider.
- The types involved
Geocoder.Provider.IpInfoDb.IpInfoDb→Geocoder.Provider.Provider
- Direction
- Provider.IpInfoDb uses Provider, so a change to Provider can break Provider.IpInfoDb, while a change to Provider.IpInfoDb can't break Provider.
- Position
- Below the diagonal: Provider.IpInfoDb uses a module listed above it, which is the healthy direction.
23→4 Provider.IpInfoDb uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.IpInfoDb uses a type in Geocoder.
- The types involved
Geocoder.Provider.IpInfoDb.IpInfoDb→Geocoder.Collection
- Direction
- Provider.IpInfoDb uses Geocoder, so a change to Geocoder can break Provider.IpInfoDb, while a change to Provider.IpInfoDb can't break Geocoder.
- Position
- Below the diagonal: Provider.IpInfoDb uses a module listed above it, which is the healthy direction.
23→5 Provider.IpInfoDb uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.IpInfoDb uses a type in Http.Provider.
- The types involved
Geocoder.Provider.IpInfoDb.IpInfoDb→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.IpInfoDb uses Http.Provider, so a change to Http.Provider can break Provider.IpInfoDb, while a change to Provider.IpInfoDb can't break Http.Provider.
- Position
- Below the diagonal: Provider.IpInfoDb uses a module listed above it, which is the healthy direction.
24→1 Provider.Ipstack uses Model✕
- Connections
- 1 pair of types, where a type in Provider.Ipstack uses a type in Model.
- The types involved
Geocoder.Provider.Ipstack.Ipstack→Geocoder.Model.AddressCollection
- Direction
- Provider.Ipstack uses Model, so a change to Model can break Provider.Ipstack, while a change to Provider.Ipstack can't break Model.
- Position
- Below the diagonal: Provider.Ipstack uses a module listed above it, which is the healthy direction.
24→2 Provider.Ipstack uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Ipstack uses a type in Query.
- The types involved
Geocoder.Provider.Ipstack.Ipstack→Geocoder.Query.GeocodeQueryGeocoder.Provider.Ipstack.Ipstack→Geocoder.Query.ReverseQuery
- Direction
- Provider.Ipstack uses Query, so a change to Query can break Provider.Ipstack, while a change to Provider.Ipstack can't break Query.
- Position
- Below the diagonal: Provider.Ipstack uses a module listed above it, which is the healthy direction.
24→3 Provider.Ipstack uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Ipstack uses a type in Provider.
- The types involved
Geocoder.Provider.Ipstack.Ipstack→Geocoder.Provider.Provider
- Direction
- Provider.Ipstack uses Provider, so a change to Provider can break Provider.Ipstack, while a change to Provider.Ipstack can't break Provider.
- Position
- Below the diagonal: Provider.Ipstack uses a module listed above it, which is the healthy direction.
24→4 Provider.Ipstack uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Ipstack uses a type in Geocoder.
- The types involved
Geocoder.Provider.Ipstack.Ipstack→Geocoder.Collection
- Direction
- Provider.Ipstack uses Geocoder, so a change to Geocoder can break Provider.Ipstack, while a change to Provider.Ipstack can't break Geocoder.
- Position
- Below the diagonal: Provider.Ipstack uses a module listed above it, which is the healthy direction.
24→5 Provider.Ipstack uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Ipstack uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Ipstack.Ipstack→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Ipstack uses Http.Provider, so a change to Http.Provider can break Provider.Ipstack, while a change to Provider.Ipstack can't break Http.Provider.
- Position
- Below the diagonal: Provider.Ipstack uses a module listed above it, which is the healthy direction.
25→2 Provider.LocationIQ uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.LocationIQ uses a type in Query.
- The types involved
Geocoder.Provider.LocationIQ.LocationIQ→Geocoder.Query.GeocodeQueryGeocoder.Provider.LocationIQ.LocationIQ→Geocoder.Query.ReverseQuery
- Direction
- Provider.LocationIQ uses Query, so a change to Query can break Provider.LocationIQ, while a change to Provider.LocationIQ can't break Query.
- Position
- Below the diagonal: Provider.LocationIQ uses a module listed above it, which is the healthy direction.
25→3 Provider.LocationIQ uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.LocationIQ uses a type in Provider.
- The types involved
Geocoder.Provider.LocationIQ.LocationIQ→Geocoder.Provider.Provider
- Direction
- Provider.LocationIQ uses Provider, so a change to Provider can break Provider.LocationIQ, while a change to Provider.LocationIQ can't break Provider.
- Position
- Below the diagonal: Provider.LocationIQ uses a module listed above it, which is the healthy direction.
25→4 Provider.LocationIQ uses Geocoder✕
- Connections
- 2 pairs of types, where a type in Provider.LocationIQ uses a type in Geocoder.
- The types involved
Geocoder.Provider.LocationIQ.LocationIQ→Geocoder.CollectionGeocoder.Provider.LocationIQ.LocationIQ→Geocoder.Location
- Direction
- Provider.LocationIQ uses Geocoder, so a change to Geocoder can break Provider.LocationIQ, while a change to Provider.LocationIQ can't break Geocoder.
- Position
- Below the diagonal: Provider.LocationIQ uses a module listed above it, which is the healthy direction.
25→5 Provider.LocationIQ uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.LocationIQ uses a type in Http.Provider.
- The types involved
Geocoder.Provider.LocationIQ.LocationIQ→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.LocationIQ uses Http.Provider, so a change to Http.Provider can break Provider.LocationIQ, while a change to Provider.LocationIQ can't break Http.Provider.
- Position
- Below the diagonal: Provider.LocationIQ uses a module listed above it, which is the healthy direction.
26→1 Provider.MapQuest uses Model✕
- Connections
- 2 pairs of types, where a type in Provider.MapQuest uses a type in Model.
- The types involved
Geocoder.Provider.MapQuest.MapQuest→Geocoder.Model.AddressCollectionGeocoder.Provider.MapQuest.MapQuest→Geocoder.Model.Bounds
- Direction
- Provider.MapQuest uses Model, so a change to Model can break Provider.MapQuest, while a change to Provider.MapQuest can't break Model.
- Position
- Below the diagonal: Provider.MapQuest uses a module listed above it, which is the healthy direction.
26→2 Provider.MapQuest uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.MapQuest uses a type in Query.
- The types involved
Geocoder.Provider.MapQuest.MapQuest→Geocoder.Query.GeocodeQueryGeocoder.Provider.MapQuest.MapQuest→Geocoder.Query.ReverseQuery
- Direction
- Provider.MapQuest uses Query, so a change to Query can break Provider.MapQuest, while a change to Provider.MapQuest can't break Query.
- Position
- Below the diagonal: Provider.MapQuest uses a module listed above it, which is the healthy direction.
26→3 Provider.MapQuest uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.MapQuest uses a type in Provider.
- The types involved
Geocoder.Provider.MapQuest.MapQuest→Geocoder.Provider.Provider
- Direction
- Provider.MapQuest uses Provider, so a change to Provider can break Provider.MapQuest, while a change to Provider.MapQuest can't break Provider.
- Position
- Below the diagonal: Provider.MapQuest uses a module listed above it, which is the healthy direction.
26→4 Provider.MapQuest uses Geocoder✕
- Connections
- 2 pairs of types, where a type in Provider.MapQuest uses a type in Geocoder.
- The types involved
Geocoder.Provider.MapQuest.MapQuest→Geocoder.CollectionGeocoder.Provider.MapQuest.MapQuest→Geocoder.Location
- Direction
- Provider.MapQuest uses Geocoder, so a change to Geocoder can break Provider.MapQuest, while a change to Provider.MapQuest can't break Geocoder.
- Position
- Below the diagonal: Provider.MapQuest uses a module listed above it, which is the healthy direction.
26→5 Provider.MapQuest uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.MapQuest uses a type in Http.Provider.
- The types involved
Geocoder.Provider.MapQuest.MapQuest→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.MapQuest uses Http.Provider, so a change to Http.Provider can break Provider.MapQuest, while a change to Provider.MapQuest can't break Http.Provider.
- Position
- Below the diagonal: Provider.MapQuest uses a module listed above it, which is the healthy direction.
27→1 Provider.MapTiler uses Model✕
- Connections
- 2 pairs of types, where a type in Provider.MapTiler uses a type in Model.
- The types involved
Geocoder.Provider.MapTiler.MapTiler→Geocoder.Model.AddressBuilderGeocoder.Provider.MapTiler.MapTiler→Geocoder.Model.Bounds
- Direction
- Provider.MapTiler uses Model, so a change to Model can break Provider.MapTiler, while a change to Provider.MapTiler can't break Model.
- Position
- Below the diagonal: Provider.MapTiler uses a module listed above it, which is the healthy direction.
27→2 Provider.MapTiler uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.MapTiler uses a type in Query.
- The types involved
Geocoder.Provider.MapTiler.MapTiler→Geocoder.Query.GeocodeQueryGeocoder.Provider.MapTiler.MapTiler→Geocoder.Query.ReverseQuery
- Direction
- Provider.MapTiler uses Query, so a change to Query can break Provider.MapTiler, while a change to Provider.MapTiler can't break Query.
- Position
- Below the diagonal: Provider.MapTiler uses a module listed above it, which is the healthy direction.
27→3 Provider.MapTiler uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.MapTiler uses a type in Provider.
- The types involved
Geocoder.Provider.MapTiler.MapTiler→Geocoder.Provider.Provider
- Direction
- Provider.MapTiler uses Provider, so a change to Provider can break Provider.MapTiler, while a change to Provider.MapTiler can't break Provider.
- Position
- Below the diagonal: Provider.MapTiler uses a module listed above it, which is the healthy direction.
27→4 Provider.MapTiler uses Geocoder✕
- Connections
- 2 pairs of types, where a type in Provider.MapTiler uses a type in Geocoder.
- The types involved
Geocoder.Provider.MapTiler.MapTiler→Geocoder.CollectionGeocoder.Provider.MapTiler.MapTiler→Geocoder.Location
- Direction
- Provider.MapTiler uses Geocoder, so a change to Geocoder can break Provider.MapTiler, while a change to Provider.MapTiler can't break Geocoder.
- Position
- Below the diagonal: Provider.MapTiler uses a module listed above it, which is the healthy direction.
27→5 Provider.MapTiler uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.MapTiler uses a type in Http.Provider.
- The types involved
Geocoder.Provider.MapTiler.MapTiler→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.MapTiler uses Http.Provider, so a change to Http.Provider can break Provider.MapTiler, while a change to Provider.MapTiler can't break Http.Provider.
- Position
- Below the diagonal: Provider.MapTiler uses a module listed above it, which is the healthy direction.
28→1 Provider.Mapbox uses Model✕
- Connections
- 2 pairs of types, where a type in Provider.Mapbox uses a type in Model.
- The types involved
Geocoder.Provider.Mapbox.Mapbox→Geocoder.Model.AddressBuilderGeocoder.Provider.Mapbox.Mapbox→Geocoder.Model.AddressCollection
- Direction
- Provider.Mapbox uses Model, so a change to Model can break Provider.Mapbox, while a change to Provider.Mapbox can't break Model.
- Position
- Below the diagonal: Provider.Mapbox uses a module listed above it, which is the healthy direction.
28→2 Provider.Mapbox uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Mapbox uses a type in Query.
- The types involved
Geocoder.Provider.Mapbox.Mapbox→Geocoder.Query.GeocodeQueryGeocoder.Provider.Mapbox.Mapbox→Geocoder.Query.ReverseQuery
- Direction
- Provider.Mapbox uses Query, so a change to Query can break Provider.Mapbox, while a change to Provider.Mapbox can't break Query.
- Position
- Below the diagonal: Provider.Mapbox uses a module listed above it, which is the healthy direction.
28→3 Provider.Mapbox uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Mapbox uses a type in Provider.
- The types involved
Geocoder.Provider.Mapbox.Mapbox→Geocoder.Provider.Provider
- Direction
- Provider.Mapbox uses Provider, so a change to Provider can break Provider.Mapbox, while a change to Provider.Mapbox can't break Provider.
- Position
- Below the diagonal: Provider.Mapbox uses a module listed above it, which is the healthy direction.
28→4 Provider.Mapbox uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Mapbox uses a type in Geocoder.
- The types involved
Geocoder.Provider.Mapbox.Mapbox→Geocoder.Collection
- Direction
- Provider.Mapbox uses Geocoder, so a change to Geocoder can break Provider.Mapbox, while a change to Provider.Mapbox can't break Geocoder.
- Position
- Below the diagonal: Provider.Mapbox uses a module listed above it, which is the healthy direction.
28→5 Provider.Mapbox uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Mapbox uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Mapbox.Mapbox→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Mapbox uses Http.Provider, so a change to Http.Provider can break Provider.Mapbox, while a change to Provider.Mapbox can't break Http.Provider.
- Position
- Below the diagonal: Provider.Mapbox uses a module listed above it, which is the healthy direction.
29→1 Provider.Mapzen uses Model✕
- Connections
- 1 pair of types, where a type in Provider.Mapzen uses a type in Model.
- The types involved
Geocoder.Provider.Mapzen.Mapzen→Geocoder.Model.AddressCollection
- Direction
- Provider.Mapzen uses Model, so a change to Model can break Provider.Mapzen, while a change to Provider.Mapzen can't break Model.
- Position
- Below the diagonal: Provider.Mapzen uses a module listed above it, which is the healthy direction.
29→2 Provider.Mapzen uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Mapzen uses a type in Query.
- The types involved
Geocoder.Provider.Mapzen.Mapzen→Geocoder.Query.GeocodeQueryGeocoder.Provider.Mapzen.Mapzen→Geocoder.Query.ReverseQuery
- Direction
- Provider.Mapzen uses Query, so a change to Query can break Provider.Mapzen, while a change to Provider.Mapzen can't break Query.
- Position
- Below the diagonal: Provider.Mapzen uses a module listed above it, which is the healthy direction.
29→3 Provider.Mapzen uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Mapzen uses a type in Provider.
- The types involved
Geocoder.Provider.Mapzen.Mapzen→Geocoder.Provider.Provider
- Direction
- Provider.Mapzen uses Provider, so a change to Provider can break Provider.Mapzen, while a change to Provider.Mapzen can't break Provider.
- Position
- Below the diagonal: Provider.Mapzen uses a module listed above it, which is the healthy direction.
29→4 Provider.Mapzen uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Mapzen uses a type in Geocoder.
- The types involved
Geocoder.Provider.Mapzen.Mapzen→Geocoder.Collection
- Direction
- Provider.Mapzen uses Geocoder, so a change to Geocoder can break Provider.Mapzen, while a change to Provider.Mapzen can't break Geocoder.
- Position
- Below the diagonal: Provider.Mapzen uses a module listed above it, which is the healthy direction.
29→5 Provider.Mapzen uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Mapzen uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Mapzen.Mapzen→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Mapzen uses Http.Provider, so a change to Http.Provider can break Provider.Mapzen, while a change to Provider.Mapzen can't break Http.Provider.
- Position
- Below the diagonal: Provider.Mapzen uses a module listed above it, which is the healthy direction.
30→1 Provider.MaxMind uses Model✕
- Connections
- 1 pair of types, where a type in Provider.MaxMind uses a type in Model.
- The types involved
Geocoder.Provider.MaxMind.MaxMind→Geocoder.Model.AddressCollection
- Direction
- Provider.MaxMind uses Model, so a change to Model can break Provider.MaxMind, while a change to Provider.MaxMind can't break Model.
- Position
- Below the diagonal: Provider.MaxMind uses a module listed above it, which is the healthy direction.
30→2 Provider.MaxMind uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.MaxMind uses a type in Query.
- The types involved
Geocoder.Provider.MaxMind.MaxMind→Geocoder.Query.GeocodeQueryGeocoder.Provider.MaxMind.MaxMind→Geocoder.Query.ReverseQuery
- Direction
- Provider.MaxMind uses Query, so a change to Query can break Provider.MaxMind, while a change to Provider.MaxMind can't break Query.
- Position
- Below the diagonal: Provider.MaxMind uses a module listed above it, which is the healthy direction.
30→3 Provider.MaxMind uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.MaxMind uses a type in Provider.
- The types involved
Geocoder.Provider.MaxMind.MaxMind→Geocoder.Provider.Provider
- Direction
- Provider.MaxMind uses Provider, so a change to Provider can break Provider.MaxMind, while a change to Provider.MaxMind can't break Provider.
- Position
- Below the diagonal: Provider.MaxMind uses a module listed above it, which is the healthy direction.
30→4 Provider.MaxMind uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.MaxMind uses a type in Geocoder.
- The types involved
Geocoder.Provider.MaxMind.MaxMind→Geocoder.Collection
- Direction
- Provider.MaxMind uses Geocoder, so a change to Geocoder can break Provider.MaxMind, while a change to Provider.MaxMind can't break Geocoder.
- Position
- Below the diagonal: Provider.MaxMind uses a module listed above it, which is the healthy direction.
30→5 Provider.MaxMind uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.MaxMind uses a type in Http.Provider.
- The types involved
Geocoder.Provider.MaxMind.MaxMind→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.MaxMind uses Http.Provider, so a change to Http.Provider can break Provider.MaxMind, while a change to Provider.MaxMind can't break Http.Provider.
- Position
- Below the diagonal: Provider.MaxMind uses a module listed above it, which is the healthy direction.
31→2 Provider.Nominatim uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Nominatim uses a type in Query.
- The types involved
Geocoder.Provider.Nominatim.Nominatim→Geocoder.Query.GeocodeQueryGeocoder.Provider.Nominatim.Nominatim→Geocoder.Query.ReverseQuery
- Direction
- Provider.Nominatim uses Query, so a change to Query can break Provider.Nominatim, while a change to Provider.Nominatim can't break Query.
- Position
- Below the diagonal: Provider.Nominatim uses a module listed above it, which is the healthy direction.
31→3 Provider.Nominatim uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Nominatim uses a type in Provider.
- The types involved
Geocoder.Provider.Nominatim.Nominatim→Geocoder.Provider.Provider
- Direction
- Provider.Nominatim uses Provider, so a change to Provider can break Provider.Nominatim, while a change to Provider.Nominatim can't break Provider.
- Position
- Below the diagonal: Provider.Nominatim uses a module listed above it, which is the healthy direction.
31→4 Provider.Nominatim uses Geocoder✕
- Connections
- 2 pairs of types, where a type in Provider.Nominatim uses a type in Geocoder.
- The types involved
Geocoder.Provider.Nominatim.Nominatim→Geocoder.CollectionGeocoder.Provider.Nominatim.Nominatim→Geocoder.Location
- Direction
- Provider.Nominatim uses Geocoder, so a change to Geocoder can break Provider.Nominatim, while a change to Provider.Nominatim can't break Geocoder.
- Position
- Below the diagonal: Provider.Nominatim uses a module listed above it, which is the healthy direction.
31→5 Provider.Nominatim uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Nominatim uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Nominatim.Nominatim→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Nominatim uses Http.Provider, so a change to Http.Provider can break Provider.Nominatim, while a change to Provider.Nominatim can't break Http.Provider.
- Position
- Below the diagonal: Provider.Nominatim uses a module listed above it, which is the healthy direction.
32→1 Provider.OpenCage uses Model✕
- Connections
- 2 pairs of types, where a type in Provider.OpenCage uses a type in Model.
- The types involved
Geocoder.Provider.OpenCage.OpenCage→Geocoder.Model.AddressBuilderGeocoder.Provider.OpenCage.OpenCage→Geocoder.Model.AddressCollection
- Direction
- Provider.OpenCage uses Model, so a change to Model can break Provider.OpenCage, while a change to Provider.OpenCage can't break Model.
- Position
- Below the diagonal: Provider.OpenCage uses a module listed above it, which is the healthy direction.
32→2 Provider.OpenCage uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.OpenCage uses a type in Query.
- The types involved
Geocoder.Provider.OpenCage.OpenCage→Geocoder.Query.GeocodeQueryGeocoder.Provider.OpenCage.OpenCage→Geocoder.Query.ReverseQuery
- Direction
- Provider.OpenCage uses Query, so a change to Query can break Provider.OpenCage, while a change to Provider.OpenCage can't break Query.
- Position
- Below the diagonal: Provider.OpenCage uses a module listed above it, which is the healthy direction.
32→3 Provider.OpenCage uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.OpenCage uses a type in Provider.
- The types involved
Geocoder.Provider.OpenCage.OpenCage→Geocoder.Provider.Provider
- Direction
- Provider.OpenCage uses Provider, so a change to Provider can break Provider.OpenCage, while a change to Provider.OpenCage can't break Provider.
- Position
- Below the diagonal: Provider.OpenCage uses a module listed above it, which is the healthy direction.
32→4 Provider.OpenCage uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.OpenCage uses a type in Geocoder.
- The types involved
Geocoder.Provider.OpenCage.OpenCage→Geocoder.Collection
- Direction
- Provider.OpenCage uses Geocoder, so a change to Geocoder can break Provider.OpenCage, while a change to Provider.OpenCage can't break Geocoder.
- Position
- Below the diagonal: Provider.OpenCage uses a module listed above it, which is the healthy direction.
32→5 Provider.OpenCage uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.OpenCage uses a type in Http.Provider.
- The types involved
Geocoder.Provider.OpenCage.OpenCage→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.OpenCage uses Http.Provider, so a change to Http.Provider can break Provider.OpenCage, while a change to Provider.OpenCage can't break Http.Provider.
- Position
- Below the diagonal: Provider.OpenCage uses a module listed above it, which is the healthy direction.
33→1 Provider.Pelias uses Model✕
- Connections
- 1 pair of types, where a type in Provider.Pelias uses a type in Model.
- The types involved
Geocoder.Provider.Pelias.Pelias→Geocoder.Model.AddressCollection
- Direction
- Provider.Pelias uses Model, so a change to Model can break Provider.Pelias, while a change to Provider.Pelias can't break Model.
- Position
- Below the diagonal: Provider.Pelias uses a module listed above it, which is the healthy direction.
33→2 Provider.Pelias uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Pelias uses a type in Query.
- The types involved
Geocoder.Provider.Pelias.Pelias→Geocoder.Query.GeocodeQueryGeocoder.Provider.Pelias.Pelias→Geocoder.Query.ReverseQuery
- Direction
- Provider.Pelias uses Query, so a change to Query can break Provider.Pelias, while a change to Provider.Pelias can't break Query.
- Position
- Below the diagonal: Provider.Pelias uses a module listed above it, which is the healthy direction.
33→3 Provider.Pelias uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Pelias uses a type in Provider.
- The types involved
Geocoder.Provider.Pelias.Pelias→Geocoder.Provider.Provider
- Direction
- Provider.Pelias uses Provider, so a change to Provider can break Provider.Pelias, while a change to Provider.Pelias can't break Provider.
- Position
- Below the diagonal: Provider.Pelias uses a module listed above it, which is the healthy direction.
33→4 Provider.Pelias uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Pelias uses a type in Geocoder.
- The types involved
Geocoder.Provider.Pelias.Pelias→Geocoder.Collection
- Direction
- Provider.Pelias uses Geocoder, so a change to Geocoder can break Provider.Pelias, while a change to Provider.Pelias can't break Geocoder.
- Position
- Below the diagonal: Provider.Pelias uses a module listed above it, which is the healthy direction.
33→5 Provider.Pelias uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Pelias uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Pelias.Pelias→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Pelias uses Http.Provider, so a change to Http.Provider can break Provider.Pelias, while a change to Provider.Pelias can't break Http.Provider.
- Position
- Below the diagonal: Provider.Pelias uses a module listed above it, which is the healthy direction.
34→2 Provider.Photon uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Photon uses a type in Query.
- The types involved
Geocoder.Provider.Photon.Photon→Geocoder.Query.GeocodeQueryGeocoder.Provider.Photon.Photon→Geocoder.Query.ReverseQuery
- Direction
- Provider.Photon uses Query, so a change to Query can break Provider.Photon, while a change to Provider.Photon can't break Query.
- Position
- Below the diagonal: Provider.Photon uses a module listed above it, which is the healthy direction.
34→3 Provider.Photon uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Photon uses a type in Provider.
- The types involved
Geocoder.Provider.Photon.Photon→Geocoder.Provider.Provider
- Direction
- Provider.Photon uses Provider, so a change to Provider can break Provider.Photon, while a change to Provider.Photon can't break Provider.
- Position
- Below the diagonal: Provider.Photon uses a module listed above it, which is the healthy direction.
34→4 Provider.Photon uses Geocoder✕
- Connections
- 2 pairs of types, where a type in Provider.Photon uses a type in Geocoder.
- The types involved
Geocoder.Provider.Photon.Photon→Geocoder.CollectionGeocoder.Provider.Photon.Photon→Geocoder.Location
- Direction
- Provider.Photon uses Geocoder, so a change to Geocoder can break Provider.Photon, while a change to Provider.Photon can't break Geocoder.
- Position
- Below the diagonal: Provider.Photon uses a module listed above it, which is the healthy direction.
34→5 Provider.Photon uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Photon uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Photon.Photon→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Photon uses Http.Provider, so a change to Http.Provider can break Provider.Photon, while a change to Provider.Photon can't break Http.Provider.
- Position
- Below the diagonal: Provider.Photon uses a module listed above it, which is the healthy direction.
35→2 Provider.PickPoint uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.PickPoint uses a type in Query.
- The types involved
Geocoder.Provider.PickPoint.PickPoint→Geocoder.Query.GeocodeQueryGeocoder.Provider.PickPoint.PickPoint→Geocoder.Query.ReverseQuery
- Direction
- Provider.PickPoint uses Query, so a change to Query can break Provider.PickPoint, while a change to Provider.PickPoint can't break Query.
- Position
- Below the diagonal: Provider.PickPoint uses a module listed above it, which is the healthy direction.
35→3 Provider.PickPoint uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.PickPoint uses a type in Provider.
- The types involved
Geocoder.Provider.PickPoint.PickPoint→Geocoder.Provider.Provider
- Direction
- Provider.PickPoint uses Provider, so a change to Provider can break Provider.PickPoint, while a change to Provider.PickPoint can't break Provider.
- Position
- Below the diagonal: Provider.PickPoint uses a module listed above it, which is the healthy direction.
35→4 Provider.PickPoint uses Geocoder✕
- Connections
- 2 pairs of types, where a type in Provider.PickPoint uses a type in Geocoder.
- The types involved
Geocoder.Provider.PickPoint.PickPoint→Geocoder.CollectionGeocoder.Provider.PickPoint.PickPoint→Geocoder.Location
- Direction
- Provider.PickPoint uses Geocoder, so a change to Geocoder can break Provider.PickPoint, while a change to Provider.PickPoint can't break Geocoder.
- Position
- Below the diagonal: Provider.PickPoint uses a module listed above it, which is the healthy direction.
35→5 Provider.PickPoint uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.PickPoint uses a type in Http.Provider.
- The types involved
Geocoder.Provider.PickPoint.PickPoint→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.PickPoint uses Http.Provider, so a change to Http.Provider can break Provider.PickPoint, while a change to Provider.PickPoint can't break Http.Provider.
- Position
- Below the diagonal: Provider.PickPoint uses a module listed above it, which is the healthy direction.
36→2 Provider.TomTom uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.TomTom uses a type in Query.
- The types involved
Geocoder.Provider.TomTom.TomTom→Geocoder.Query.GeocodeQueryGeocoder.Provider.TomTom.TomTom→Geocoder.Query.ReverseQuery
- Direction
- Provider.TomTom uses Query, so a change to Query can break Provider.TomTom, while a change to Provider.TomTom can't break Query.
- Position
- Below the diagonal: Provider.TomTom uses a module listed above it, which is the healthy direction.
36→3 Provider.TomTom uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.TomTom uses a type in Provider.
- The types involved
Geocoder.Provider.TomTom.TomTom→Geocoder.Provider.Provider
- Direction
- Provider.TomTom uses Provider, so a change to Provider can break Provider.TomTom, while a change to Provider.TomTom can't break Provider.
- Position
- Below the diagonal: Provider.TomTom uses a module listed above it, which is the healthy direction.
36→4 Provider.TomTom uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.TomTom uses a type in Geocoder.
- The types involved
Geocoder.Provider.TomTom.TomTom→Geocoder.Collection
- Direction
- Provider.TomTom uses Geocoder, so a change to Geocoder can break Provider.TomTom, while a change to Provider.TomTom can't break Geocoder.
- Position
- Below the diagonal: Provider.TomTom uses a module listed above it, which is the healthy direction.
36→5 Provider.TomTom uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.TomTom uses a type in Http.Provider.
- The types involved
Geocoder.Provider.TomTom.TomTom→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.TomTom uses Http.Provider, so a change to Http.Provider can break Provider.TomTom, while a change to Provider.TomTom can't break Http.Provider.
- Position
- Below the diagonal: Provider.TomTom uses a module listed above it, which is the healthy direction.
37→1 Provider.Yandex uses Model✕
- Connections
- 1 pair of types, where a type in Provider.Yandex uses a type in Model.
- The types involved
Geocoder.Provider.Yandex.Yandex→Geocoder.Model.AddressCollection
- Direction
- Provider.Yandex uses Model, so a change to Model can break Provider.Yandex, while a change to Provider.Yandex can't break Model.
- Position
- Below the diagonal: Provider.Yandex uses a module listed above it, which is the healthy direction.
37→2 Provider.Yandex uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.Yandex uses a type in Query.
- The types involved
Geocoder.Provider.Yandex.Yandex→Geocoder.Query.GeocodeQueryGeocoder.Provider.Yandex.Yandex→Geocoder.Query.ReverseQuery
- Direction
- Provider.Yandex uses Query, so a change to Query can break Provider.Yandex, while a change to Provider.Yandex can't break Query.
- Position
- Below the diagonal: Provider.Yandex uses a module listed above it, which is the healthy direction.
37→3 Provider.Yandex uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.Yandex uses a type in Provider.
- The types involved
Geocoder.Provider.Yandex.Yandex→Geocoder.Provider.Provider
- Direction
- Provider.Yandex uses Provider, so a change to Provider can break Provider.Yandex, while a change to Provider.Yandex can't break Provider.
- Position
- Below the diagonal: Provider.Yandex uses a module listed above it, which is the healthy direction.
37→4 Provider.Yandex uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.Yandex uses a type in Geocoder.
- The types involved
Geocoder.Provider.Yandex.Yandex→Geocoder.Collection
- Direction
- Provider.Yandex uses Geocoder, so a change to Geocoder can break Provider.Yandex, while a change to Provider.Yandex can't break Geocoder.
- Position
- Below the diagonal: Provider.Yandex uses a module listed above it, which is the healthy direction.
37→5 Provider.Yandex uses Http.Provider✕
- Connections
- 1 pair of types, where a type in Provider.Yandex uses a type in Http.Provider.
- The types involved
Geocoder.Provider.Yandex.Yandex→Geocoder.Http.Provider.AbstractHttpProvider
- Direction
- Provider.Yandex uses Http.Provider, so a change to Http.Provider can break Provider.Yandex, while a change to Provider.Yandex can't break Http.Provider.
- Position
- Below the diagonal: Provider.Yandex uses a module listed above it, which is the healthy direction.
38→1 Plugin.Plugin uses Model✕
- Connections
- 1 pair of types, where a type in Plugin.Plugin uses a type in Model.
- The types involved
Geocoder.Plugin.Plugin.BoundsPlugin→Geocoder.Model.Bounds
- Direction
- Plugin.Plugin uses Model, so a change to Model can break Plugin.Plugin, while a change to Plugin.Plugin can't break Model.
- Position
- Below the diagonal: Plugin.Plugin uses a module listed above it, which is the healthy direction.
38→2 Plugin.Plugin uses Query✕
- Connections
- 6 pairs of types, where a type in Plugin.Plugin uses a type in Query.
- The types involved
Geocoder.Plugin.Plugin.BoundsPlugin→Geocoder.Query.QueryGeocoder.Plugin.Plugin.CachePlugin→Geocoder.Query.QueryGeocoder.Plugin.Plugin.LimitPlugin→Geocoder.Query.QueryGeocoder.Plugin.Plugin.LocalePlugin→Geocoder.Query.QueryGeocoder.Plugin.Plugin.LoggerPlugin→Geocoder.Query.QueryGeocoder.Plugin.Plugin.QueryDataPlugin→Geocoder.Query.Query
- Direction
- Plugin.Plugin uses Query, so a change to Query can break Plugin.Plugin, while a change to Plugin.Plugin can't break Query.
- Position
- Below the diagonal: Plugin.Plugin uses a module listed above it, which is the healthy direction.
38→6 Plugin.Plugin uses Plugin✕
- Connections
- 6 pairs of types, where a type in Plugin.Plugin uses a type in Plugin.
- The types involved
Geocoder.Plugin.Plugin.BoundsPlugin→Geocoder.Plugin.PluginGeocoder.Plugin.Plugin.CachePlugin→Geocoder.Plugin.PluginGeocoder.Plugin.Plugin.LimitPlugin→Geocoder.Plugin.PluginGeocoder.Plugin.Plugin.LocalePlugin→Geocoder.Plugin.PluginGeocoder.Plugin.Plugin.LoggerPlugin→Geocoder.Plugin.PluginGeocoder.Plugin.Plugin.QueryDataPlugin→Geocoder.Plugin.Plugin
- Direction
- Plugin.Plugin uses Plugin, so a change to Plugin can break Plugin.Plugin, while a change to Plugin.Plugin can't break Plugin.
- Position
- Below the diagonal: Plugin.Plugin uses a module listed above it, which is the healthy direction.
39→2 Provider.GeocodeEarth uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.GeocodeEarth uses a type in Query.
- The types involved
Geocoder.Provider.GeocodeEarth.GeocodeEarth→Geocoder.Query.GeocodeQueryGeocoder.Provider.GeocodeEarth.GeocodeEarth→Geocoder.Query.ReverseQuery
- Direction
- Provider.GeocodeEarth uses Query, so a change to Query can break Provider.GeocodeEarth, while a change to Provider.GeocodeEarth can't break Query.
- Position
- Below the diagonal: Provider.GeocodeEarth uses a module listed above it, which is the healthy direction.
39→3 Provider.GeocodeEarth uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.GeocodeEarth uses a type in Provider.
- The types involved
Geocoder.Provider.GeocodeEarth.GeocodeEarth→Geocoder.Provider.Provider
- Direction
- Provider.GeocodeEarth uses Provider, so a change to Provider can break Provider.GeocodeEarth, while a change to Provider.GeocodeEarth can't break Provider.
- Position
- Below the diagonal: Provider.GeocodeEarth uses a module listed above it, which is the healthy direction.
39→4 Provider.GeocodeEarth uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.GeocodeEarth uses a type in Geocoder.
- The types involved
Geocoder.Provider.GeocodeEarth.GeocodeEarth→Geocoder.Collection
- Direction
- Provider.GeocodeEarth uses Geocoder, so a change to Geocoder can break Provider.GeocodeEarth, while a change to Provider.GeocodeEarth can't break Geocoder.
- Position
- Below the diagonal: Provider.GeocodeEarth uses a module listed above it, which is the healthy direction.
39→33 Provider.GeocodeEarth uses Provider.Pelias✕
- Connections
- 1 pair of types, where a type in Provider.GeocodeEarth uses a type in Provider.Pelias.
- The types involved
Geocoder.Provider.GeocodeEarth.GeocodeEarth→Geocoder.Provider.Pelias.Pelias
- Direction
- Provider.GeocodeEarth uses Provider.Pelias, so a change to Provider.Pelias can break Provider.GeocodeEarth, while a change to Provider.GeocodeEarth can't break Provider.Pelias.
- Position
- Below the diagonal: Provider.GeocodeEarth uses a module listed above it, which is the healthy direction.
40→2 Provider.OpenRouteService uses Query✕
- Connections
- 2 pairs of types, where a type in Provider.OpenRouteService uses a type in Query.
- The types involved
Geocoder.Provider.OpenRouteService.OpenRouteService→Geocoder.Query.GeocodeQueryGeocoder.Provider.OpenRouteService.OpenRouteService→Geocoder.Query.ReverseQuery
- Direction
- Provider.OpenRouteService uses Query, so a change to Query can break Provider.OpenRouteService, while a change to Provider.OpenRouteService can't break Query.
- Position
- Below the diagonal: Provider.OpenRouteService uses a module listed above it, which is the healthy direction.
40→3 Provider.OpenRouteService uses Provider✕
- Connections
- 1 pair of types, where a type in Provider.OpenRouteService uses a type in Provider.
- The types involved
Geocoder.Provider.OpenRouteService.OpenRouteService→Geocoder.Provider.Provider
- Direction
- Provider.OpenRouteService uses Provider, so a change to Provider can break Provider.OpenRouteService, while a change to Provider.OpenRouteService can't break Provider.
- Position
- Below the diagonal: Provider.OpenRouteService uses a module listed above it, which is the healthy direction.
40→4 Provider.OpenRouteService uses Geocoder✕
- Connections
- 1 pair of types, where a type in Provider.OpenRouteService uses a type in Geocoder.
- The types involved
Geocoder.Provider.OpenRouteService.OpenRouteService→Geocoder.Collection
- Direction
- Provider.OpenRouteService uses Geocoder, so a change to Geocoder can break Provider.OpenRouteService, while a change to Provider.OpenRouteService can't break Geocoder.
- Position
- Below the diagonal: Provider.OpenRouteService uses a module listed above it, which is the healthy direction.
40→33 Provider.OpenRouteService uses Provider.Pelias✕
- Connections
- 1 pair of types, where a type in Provider.OpenRouteService uses a type in Provider.Pelias.
- The types involved
Geocoder.Provider.OpenRouteService.OpenRouteService→Geocoder.Provider.Pelias.Pelias
- Direction
- Provider.OpenRouteService uses Provider.Pelias, so a change to Provider.Pelias can break Provider.OpenRouteService, while a change to Provider.OpenRouteService can't break Provider.Pelias.
- Position
- Below the diagonal: Provider.OpenRouteService 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 25 | High / Critical |
Roadmap
Top priorities: Resolve the 47 Orphaned file finding(s) in Knowledge Freshness — start with GoogleMaps.php, MaxMind.php, GoogleMapsPlaces.php; 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; Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 47 Orphaned file finding(s) in Knowledge Freshness — start with GoogleMaps.php, MaxMind.php, GoogleMapsPlaces.php. | +13.6 pts | Medium | Knowledge Freshness |
| 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. | +12.4 pts | Medium | Architecture documentation |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +4.4 pts | Medium | Nullable reference types |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.1 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 20 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.0 pts | Low | Static Analysis (SAST) |
| Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). | +0.9 pts | Low | Documentation Quality |
| Resolve the 4 No assertions finding(s) in Test Quality — start with GpxTest.php (4). | +0.6 pts | Low | Test Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Provider/LocationIQ/LocationIQ.php | 7.1 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| src/Provider/GeoIPs/GeoIPs.php | 7.2 | Mixed | Cyclomatic Complexity: GeoIPs.executeQuery (cyclomatic 22) |
| src/Provider/MapQuest/MapQuest.php | 7.2 | Mixed | Cyclomatic Complexity: MapQuest.parseResponseContent (cyclomatic 21) |
| src/Provider/GeoPlugin/GeoPlugin.php | 7.2 | Mixed | Cyclomatic Complexity: GeoPlugin.executeQuery (cyclomatic 20) |
| src/Common/Tests/Dumper/GpxTest.php | 7.2 | Mixed | Test Quality: No assertions: testDump |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/Provider/GoogleMapsPlaces/GoogleMapsPlaces.php | 7.4 | Mixed | Cyclomatic Complexity: GoogleMapsPlaces.fetchUrl (cyclomatic 21) |
| src/Provider/Mapzen/Mapzen.php | 7.4 | Mixed | Cyclomatic Complexity: Mapzen.executeQuery (cyclomatic 20) |
| src/Provider/OpenCage/OpenCage.php | 7.4 | Mixed | Cyclomatic Complexity: OpenCage.executeQuery (cyclomatic 17) |
| src/Provider/GoogleMaps/GoogleMaps.php | 7.4 | Mixed | Cognitive Complexity: GoogleMaps.fetchUrl (cognitive 19) |
| src/Provider/MapTiler/MapTiler.php | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| src/Provider/FreeGeoIp/FreeGeoIp.php | 7.8 | Mixed | Cyclomatic Complexity: FreeGeoIp.geocodeQuery (cyclomatic 21) |
| src/Provider/Yandex/Yandex.php | 7.8 | Mixed | Cyclomatic Complexity: Yandex.executeQuery (cyclomatic 20) |
| src/Provider/GeoIP2/GeoIP2.php | 7.8 | Mixed | Cyclomatic Complexity: GeoIP2.geocodeQuery (cyclomatic 19) |
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 38 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 38 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, 149 of 154 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 (.php) 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 (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. 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 — 4 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — 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 — this repository declares a composer.json but commits no composer.lock this pass can read, so the set of packages it installs is not on disk: its composer.json states version CONSTRAINTS, and Composer's guidance is that a library leaves the lock uncommitted. Producing the graph needs Composer's solver, which this pass does not run, and grading whichever release happens to be newest today would be a verdict about a dependency graph nobody resolved. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — 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. All 55 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 55 of the 112 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — 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.
- 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 PHP 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 PHP 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin 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.
- X12 Unreachable branch — 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, Python, Dart, Ruby, Scala, Kotlin, Java and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Java or Rust 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.
- X13 Undrained process stream — 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, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java 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.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Python, Dart, Ruby, Scala, Kotlin or Rust 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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- 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.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GeoIPs.executeQuery at 22. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being GoogleMaps.updateAddressComponent at 32 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Provider/GoogleMaps/GoogleMaps.php (GoogleMaps.updateAddressComponent at 32). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GeoIPs.executeQuery (cyclomatic 22), FreeGeoIp.geocodeQuery (cyclomatic 21), GoogleMapsPlaces.fetchUrl (cyclomatic 21). — 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 10 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
15 method(s) exceeded the cognitive complexity threshold of 15; the worst was MapQuest.parseResponseContent at 45.
What to do
- Bring the 15 bodies over 15 down to 15 or less in Cognitive Complexity — start with MapQuest.parseResponseContent (cognitive 45), GoogleMapsPlaces.fetchUrl (cognitive 35), Yandex.executeQuery (cognitive 31). — 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 15 together lifts Cognitive Complexity from 7.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with GoogleAddress.php. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
14 duplicated block group(s) detected. 5.1 % of the production lines (616 of 12,079) are in a reported copy. A further 17 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 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with GeoPlugin.php, AzureMaps.php, LocationIQ.php. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (30 corresponding lines) finding(s) in Code Duplication — start with LocationIQ.php, IP2LocationBinary.php. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with StatefulGeocoder.php, MapQuest.php. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
42 production modules (Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 41 of the 42 (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)
4 of 49 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with CountryInfo.php, HereAddress.php, GeocodeQuery.php. — One of this dimension's main actionable groups (4 warning-level).
D10 · Test Quality
0 skipped, 4 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 74 tests.
What to do
- Resolve the 4 No assertions finding(s) in Test Quality — start with GpxTest.php (4). — One of this dimension's main actionable groups (4 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 12079 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 2 documentation facets pass in full; short on: F2 example. 48 document(s) read across 42 unit(s).
D26 · Project Cohesion
0 of 42 build units (Composer) flagged as possibly oversized/incoherent.
D27 · Navigability
63 % of calls cross a namespace and 9 % go through an interface, but 12 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
25 finding(s): 0 critical, 25 high, 0 medium, 0 low. 20 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 20 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (21 issue-level, 1 of them charged here).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
47 of 55 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/Provider/GoogleMaps/GoogleMaps.php. Counted over 55 of the 112 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 47 Orphaned file finding(s) in Knowledge Freshness — start with GoogleMaps.php, MaxMind.php, GoogleMapsPlaces.php. — One of this dimension's main actionable groups (47 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
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
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
X14 · Bypassable address classification
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X4 · Structured logging
X5 · Nullable reference types
- 0/1 of this repository's PHPStan/Psalm configuration(s) run at a level that checks null — PHPStan level 8 or above (`max` included), or Psalm `errorLevel` 3 or below (Psalm's default, with none stated, is 1). A PHPStan level written neither in the file nor in an include inside the repository is 0, PHPStan's own default. Below those levels the checker removes `null` from a union before any rule looks, so `$order->customer()->name()` on a `?Customer` passes, and the first null reaching it is an `Error: Call to a member function name() on null` in production.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 70.1 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97.3 | Exemplary | Strongest area. |
| Maturity | 50.3 | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 89.0 | Strong | Solid. |
| Security | 80.7 | Strong | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 4 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 6 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 — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's PHP 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 — Not applicable: PHP builds its object graph per request and shares none of it between requests.
- 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend 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, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source 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, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D11 Test Reliability — Test reliability not included — no .php test runner
- D12 Dependency Hygiene — Not scored — 4 direct Composer requirement(s) were read, but the outdated signal needs Packagist, and no committed composer.lock resolves them to releases, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Composer package licences not graded — this repository commits no composer.lock and this pass does not run Composer's solver
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
- D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed PHP surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (Provider), which is a layered codebase, not two contexts. 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 .php, 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
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- 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) — 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.
- 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.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet).
- 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 (6 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit))
- 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
- M4 Documentation accuracy — Not applicable: the 48 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's PHP source (42 module(s), 112 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 PHP 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 PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.json, 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.
- PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- 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.
- X1 Async correctness — 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
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not 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: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 25 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 69 finding(s)
- No assertions: testDump src/Common/Tests/Dumper/GpxTest.php:35
- No assertions: testDumpWithData src/Common/Tests/Dumper/GpxTest.php:59
- No assertions: testDumpWithBounds src/Common/Tests/Dumper/GpxTest.php:87
- No assertions: testDumpWithName src/Common/Tests/Dumper/GpxTest.php:125
- Low cohesion: CountryInfo (LCOM4 14) src/Provider/Geonames/Model/CountryInfo.php:21
- Low cohesion: HereAddress (LCOM4 9) src/Provider/Here/Model/HereAddress.php:20
- Low cohesion: GeocodeQuery (LCOM4 6) src/Common/Query/GeocodeQuery.php:22
- Low cohesion: ReverseQuery (LCOM4 5) src/Common/Query/ReverseQuery.php:21
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (8 lines × 2) src/Provider/GeoPlugin/GeoPlugin.php:37
- Duplicated block (8 lines × 2) src/Provider/AzureMaps/AzureMaps.php:223
- Duplicated block (8 lines × 2) src/Provider/LocationIQ/LocationIQ.php:153
- Edited copy of a member (30 corresponding lines) src/Provider/LocationIQ/LocationIQ.php:127
- Edited copy of a member (30 corresponding lines) src/Provider/IP2LocationBinary/IP2LocationBinary.php:62
- Edited copy of a member (11 corresponding lines) src/Common/StatefulGeocoder.php:54
- Edited copy of a member (11 corresponding lines) src/Provider/MapQuest/MapQuest.php:168
- Edited copy of a member (9 corresponding lines) src/Plugin/PluginProvider.php:62
- Edited copy of a member (9 corresponding lines) src/Plugin/Plugin/CachePlugin.php:54
- Edited copy of a member (7 corresponding lines) src/Common/Model/AddressBuilder.php:131
- Edited copy of a member (7 corresponding lines) src/Provider/MapQuest/MapQuest.php:110
- GeoIPs.executeQuery (cyclomatic 22) src/Provider/GeoIPs/GeoIPs.php:108
- FreeGeoIp.geocodeQuery (cyclomatic 21) src/Provider/FreeGeoIp/FreeGeoIp.php:43
- GoogleMapsPlaces.fetchUrl (cyclomatic 21) src/Provider/GoogleMapsPlaces/GoogleMapsPlaces.php:295
- MapQuest.parseResponseContent (cyclomatic 21) src/Provider/MapQuest/MapQuest.php:276
- GeoPlugin.executeQuery (cyclomatic 20) src/Provider/GeoPlugin/GeoPlugin.php:61
- Mapzen.executeQuery (cyclomatic 20) src/Provider/Mapzen/Mapzen.php:96
- Yandex.executeQuery (cyclomatic 20) src/Provider/Yandex/Yandex.php:97
- GeoIP2.geocodeQuery (cyclomatic 19) src/Provider/GeoIP2/GeoIP2.php:44
- Pelias.executeQuery (cyclomatic 18) src/Provider/Pelias/Pelias.php:108
- OpenCage.executeQuery (cyclomatic 17) src/Provider/OpenCage/OpenCage.php:102
- MapQuest.parseResponseContent (cognitive 45) src/Provider/MapQuest/MapQuest.php:276
- GoogleMapsPlaces.fetchUrl (cognitive 35) src/Provider/GoogleMapsPlaces/GoogleMapsPlaces.php:295
- Yandex.executeQuery (cognitive 31) src/Provider/Yandex/Yandex.php:97
- Mapzen.executeQuery (cognitive 30) src/Provider/Mapzen/Mapzen.php:96
- GeoIP2.geocodeQuery (cognitive 25) src/Provider/GeoIP2/GeoIP2.php:44
- Pelias.executeQuery (cognitive 24) src/Provider/Pelias/Pelias.php:108
- ArcGISOnline.geocodeQuery (cognitive 23) src/Provider/ArcGISOnline/ArcGISOnline.php:95
- GeoIPs.executeQuery (cognitive 23) src/Provider/GeoIPs/GeoIPs.php:108
- OpenCage.executeQuery (cognitive 22) src/Provider/OpenCage/OpenCage.php:102
- FreeGeoIp.geocodeQuery (cognitive 20) src/Provider/FreeGeoIp/FreeGeoIp.php:43
- GeoPlugin.executeQuery (cognitive 19) src/Provider/GeoPlugin/GeoPlugin.php:61
- GoogleMaps.fetchUrl (cognitive 19) src/Provider/GoogleMaps/GoogleMaps.php:200
- Mapbox.fetchUrl (cognitive 19) src/Provider/Mapbox/Mapbox.php:249
- Nominatim.jsonResultToLocation (cognitive 19) src/Provider/Nominatim/Nominatim.php:177
- GoogleMapsPlaces.buildNearbySearchQuery (cognitive 17) src/Provider/GoogleMapsPlaces/GoogleMapsPlaces.php:207
- TooManyMethods: GoogleAddress src/Provider/GoogleMaps/Model/GoogleAddress.php:22
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/Provider/MapTiler/MapTiler.php:56
- Edited copy of a member (24 corresponding lines) src/Provider/GoogleMaps/GoogleMaps.php:407
- Edited copy of a member (15 corresponding lines) src/Http/Provider/AbstractHttpProvider.php:107
- Edited copies of one member (4 members, 16+ corresponding lines) src/Provider/GeoIPs/GeoIPs.php:80
- Edited copies of one member (3 members, 11+ corresponding lines) src/Provider/GeoPlugin/GeoPlugin.php:37
- Edited copies of one member (3 members, 6+ corresponding lines) src/Provider/Geonames/Geonames.php:85
- Edited copies of one member (3 members, 7+ corresponding lines) src/Provider/BingMaps/BingMaps.php:63
- Edited copies of one member (3 members, 8+ corresponding lines) src/Common/Dumper/Kml.php:24
- Edited copy of a member (10 corresponding lines) src/Provider/MapTiler/MapTiler.php:151
- Duplicated block (25 lines × 2) src/Provider/GraphHopper/GraphHopper.php:103
- Duplicated block (23–24 lines × 2) src/Provider/LocationIQ/LocationIQ.php:79
- Duplicated block (19 lines × 2) src/Provider/LocationIQ/LocationIQ.php:127
- Duplicated block (13–14 lines × 2) src/Provider/GoogleMaps/GoogleMaps.php:418
- Duplicated block (16 lines × 2) src/Provider/LocationIQ/LocationIQ.php:107
- Duplicated block (14 lines × 2) src/Provider/Photon/Photon.php:67
- Duplicated block (11–13 lines × 2) src/Provider/GeoIPs/GeoIPs.php:80
- Duplicated block (13 lines × 2) src/Provider/Photon/Photon.php:83
- Duplicated block (12 lines × 2) src/Provider/OpenCage/OpenCage.php:124
- Duplicated block (10 lines × 4) src/Provider/MapTiler/MapTiler.php:67
- Duplicated block (7 lines × 3) src/Provider/Mapzen/Mapzen.php:210
Minor — 60 finding(s)
- Orphaned file src/Provider/GoogleMaps/GoogleMaps.php:1
- Orphaned file src/Provider/MaxMind/MaxMind.php:1
- Orphaned file src/Provider/GoogleMapsPlaces/GoogleMapsPlaces.php:1
- Orphaned file src/Provider/MapQuest/MapQuest.php:1
- Orphaned file src/Provider/Mapbox/Mapbox.php:1
- Orphaned file src/Provider/Here/Here.php:1
- Orphaned file src/Provider/GoogleMaps/Model/GoogleAddress.php:1
- Orphaned file src/Provider/OpenCage/OpenCage.php:1
- Orphaned file src/Provider/ArcGISOnline/ArcGISOnline.php:1
- Orphaned file src/Provider/AzureMaps/AzureMaps.php:1
- Orphaned file src/Common/Model/Address.php:1
- Orphaned file src/Http/Provider/AbstractHttpProvider.php:1
- Orphaned file src/Provider/Geonames/Geonames.php:1
- Orphaned file src/Provider/AlgoliaPlaces/AlgoliaPlaces.php:1
- Orphaned file src/Provider/Mapzen/Mapzen.php:1
- Orphaned file src/Provider/GeoIPs/GeoIPs.php:1
- Orphaned file src/Provider/LocationIQ/LocationIQ.php:1
- Orphaned file src/Provider/GoogleMapsPlaces/Model/GooglePlace.php:1
- Orphaned file src/Provider/Yandex/Yandex.php:1
- Orphaned file src/Provider/PickPoint/PickPoint.php:1
- Orphaned file src/Provider/Geonames/Model/CountryInfo.php:1
- Orphaned file src/Common/Model/AddressBuilder.php:1
- Orphaned file src/Provider/TomTom/TomTom.php:1
- Orphaned file src/Provider/IpInfoDb/IpInfoDb.php:1
- Orphaned file src/Provider/BingMaps/BingMaps.php:1
- Duplicated predicate src/Provider/MapTiler/MapTiler.php:67
- Duplicated predicate src/Provider/MapQuest/MapQuest.php:280
- Duplicated predicate src/Http/Provider/AbstractHttpProvider.php:110
- Duplicated predicate src/Provider/Mapzen/Mapzen.php:211
- Duplicated predicate src/Provider/GeoPlugin/GeoPlugin.php:92
- Duplicated predicate src/Provider/GoogleMaps/GoogleMaps.php:418
- Documentation: no build, run or usage example src/Provider/GeoIPs/README.md:1
- Documentation: no build, run or usage example src/Provider/Mapzen/README.md:1
- Scattered collaborators
- Concentrated knowledge decay
- No ADRs
- No architecture diagram/doc
- PHP static analysis does not check null everywhere
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-3372669b898b44b9a1701476e00b7838/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-3372669b898b44b9a1701476e00b7838/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=552" --report-format json --report-path /tmp/watchdog-gitleaks-3372669b898b44b9a1701476e00b7838/history-2.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-2.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-3372669b898b44b9a1701476e00b7838/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 25 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |
| 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. | 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 | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json — not scanned yet). | 0 | — |