Executive summary
flannel-io/flannel falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 68.7 out of 100 and is rated Adequate, and all 18 of its critical findings are security problems.
Production Readiness, at 63.0, is the weakest lens and counts most in the score. The best first step for the work it takes is pinning the dependencies to tagged releases, worth about 3.0 points. Adding tests for untested code would lift Production Readiness itself, worth about 5.6 points. Raising Production Readiness to 70 would lift the score to about 71.5.
Fifteen settings leave the servers or containers unsafe. One automatic update takes new releases before a bad one can be spotted, and one place in the code runs text as code, which an attacker could use. Correcting the unsafe settings, setting a waiting period for automatic updates and replacing text run as code with direct calls would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code.
The product code is 10,867 lines, about €21,000 to rebuild.
If Production Readiness rose from 63.0 to 70, the lowest score rated Strong, the score would rise from 68.7 to about 71.5.
Rebuild cost: about €21,000 · Estimate
| Cost to rebuild | €7,100 to €36,000, for 118 to 374 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 69. 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: 10,867 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 com/flannel-io/flannel/cmd/install_conf | 2 com/flannel-io/flannel/pkg/ip | 3 com/flannel-io/flannel/pkg/mac | 4 com/flannel-io/flannel/pkg/ns | 5 com/flannel-io/flannel/pkg/powershell | 6 com/flannel-io/flannel/pkg/retry | 7 com/flannel-io/flannel/pkg/routing | 8 com/flannel-io/flannel/pkg/utils | 9 com/flannel-io/flannel/pkg/version | 10 com/flannel-io/flannel/pkg/lease | 11 com/flannel-io/flannel/pkg/subnet | 12 com/flannel-io/flannel/pkg/trafficmngr | 13 com/flannel-io/flannel | 14 com/flannel-io/flannel/pkg/backend | 15 com/flannel-io/flannel/pkg/subnet/etcd | 16 com/flannel-io/flannel/pkg/subnet/kube | 17 com/flannel-io/flannel/pkg/trafficmngr/iptables | 18 com/flannel-io/flannel/pkg/trafficmngr/nftables | 19 com/flannel-io/flannel/pkg/backend/alloc | 20 com/flannel-io/flannel/pkg/backend/extension | 21 com/flannel-io/flannel/pkg/backend/hostgw | 22 com/flannel-io/flannel/pkg/backend/ipip | 23 com/flannel-io/flannel/pkg/backend/ipsec | 24 com/flannel-io/flannel/pkg/backend/tencentvpc | 25 com/flannel-io/flannel/pkg/backend/udp | 26 com/flannel-io/flannel/pkg/backend/vxlan | 27 com/flannel-io/flannel/pkg/backend/wireguard | 28 com/flannel-io/flannel/pkg/ipmatch |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com/flannel-io/flannel/cmd/install_conf | ||||||||||||||||||||||||||||
| 2 com/flannel-io/flannel/pkg/ip | ||||||||||||||||||||||||||||
| 3 com/flannel-io/flannel/pkg/mac | ||||||||||||||||||||||||||||
| 4 com/flannel-io/flannel/pkg/ns | ||||||||||||||||||||||||||||
| 5 com/flannel-io/flannel/pkg/powershell | ||||||||||||||||||||||||||||
| 6 com/flannel-io/flannel/pkg/retry | ||||||||||||||||||||||||||||
| 7 com/flannel-io/flannel/pkg/routing | ||||||||||||||||||||||||||||
| 8 com/flannel-io/flannel/pkg/utils | ||||||||||||||||||||||||||||
| 9 com/flannel-io/flannel/pkg/version | ||||||||||||||||||||||||||||
| 10 com/flannel-io/flannel/pkg/lease | 4 | |||||||||||||||||||||||||||
| 11 com/flannel-io/flannel/pkg/subnet | 8 | 5 | ||||||||||||||||||||||||||
| 12 com/flannel-io/flannel/pkg/trafficmngr | 2 | 1 | ||||||||||||||||||||||||||
| 13 com/flannel-io/flannel | 2 | 2 | 1 | |||||||||||||||||||||||||
| 14 com/flannel-io/flannel/pkg/backend | 1 | 3 | 4 | |||||||||||||||||||||||||
| 15 com/flannel-io/flannel/pkg/subnet/etcd | 13 | 18 | 4 | |||||||||||||||||||||||||
| 16 com/flannel-io/flannel/pkg/subnet/kube | 4 | 5 | 4 | |||||||||||||||||||||||||
| 17 com/flannel-io/flannel/pkg/trafficmngr/iptables | 2 | 1 | 3 | |||||||||||||||||||||||||
| 18 com/flannel-io/flannel/pkg/trafficmngr/nftables | 2 | 1 | 1 | |||||||||||||||||||||||||
| 19 com/flannel-io/flannel/pkg/backend/alloc | 3 | 4 | ||||||||||||||||||||||||||
| 20 com/flannel-io/flannel/pkg/backend/extension | 2 | 4 | 6 | |||||||||||||||||||||||||
| 21 com/flannel-io/flannel/pkg/backend/hostgw | 3 | 4 | ||||||||||||||||||||||||||
| 22 com/flannel-io/flannel/pkg/backend/ipip | 1 | 1 | 3 | 4 | ||||||||||||||||||||||||
| 23 com/flannel-io/flannel/pkg/backend/ipsec | 4 | 4 | 5 | |||||||||||||||||||||||||
| 24 com/flannel-io/flannel/pkg/backend/tencentvpc | 3 | 4 | ||||||||||||||||||||||||||
| 25 com/flannel-io/flannel/pkg/backend/udp | 3 | 2 | 4 | 5 | ||||||||||||||||||||||||
| 26 com/flannel-io/flannel/pkg/backend/vxlan | 6 | 3 | 5 | 5 | ||||||||||||||||||||||||
| 27 com/flannel-io/flannel/pkg/backend/wireguard | 6 | 4 | 4 | 6 | ||||||||||||||||||||||||
| 28 com/flannel-io/flannel/pkg/ipmatch | 1 |
10→2 com/flannel-io/flannel/pkg/lease uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/lease uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/lease.Lease→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/lease.Lease→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/lease.LeaseAttrs→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/lease.LeaseAttrs→github.com/flannel-io/flannel/pkg/ip.IP6
- Direction
- com/flannel-io/flannel/pkg/lease uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/lease, while a change to com/flannel-io/flannel/pkg/lease can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/lease uses a module listed above it, which is the healthy direction.
11→2 com/flannel-io/flannel/pkg/subnet uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 8 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/subnet.Config→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/subnet.Config→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet.Config→github.com/flannel-io/flannel/pkg/ip.IP6github.com/flannel-io/flannel/pkg/subnet.Config→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet.Manager→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet.Manager→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet.subnet→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet.subnet→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel/pkg/subnet uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/subnet, while a change to com/flannel-io/flannel/pkg/subnet can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet uses a module listed above it, which is the healthy direction.
11→10 com/flannel-io/flannel/pkg/subnet uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 5 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/subnet.Manager→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet.Manager→github.com/flannel-io/flannel/pkg/lease.LeaseAttrsgithub.com/flannel-io/flannel/pkg/subnet.Manager→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResultgithub.com/flannel-io/flannel/pkg/subnet.subnet→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/subnet.subnet→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/subnet uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/subnet, while a change to com/flannel-io/flannel/pkg/subnet can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet uses a module listed above it, which is the healthy direction.
12→2 com/flannel-io/flannel/pkg/trafficmngr uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel/pkg/trafficmngr uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr.TrafficManager→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/trafficmngr.TrafficManager→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel/pkg/trafficmngr uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/trafficmngr, while a change to com/flannel-io/flannel/pkg/trafficmngr can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr uses a module listed above it, which is the healthy direction.
12→10 com/flannel-io/flannel/pkg/trafficmngr uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/trafficmngr uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr.TrafficManager→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/trafficmngr uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/trafficmngr, while a change to com/flannel-io/flannel/pkg/trafficmngr can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr uses a module listed above it, which is the healthy direction.
13→2 com/flannel-io/flannel uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel.main→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel.main→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel, while a change to com/flannel-io/flannel can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel uses a module listed above it, which is the healthy direction.
13→11 com/flannel-io/flannel uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel.main→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel.main→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel, while a change to com/flannel-io/flannel can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel uses a module listed above it, which is the healthy direction.
13→12 com/flannel-io/flannel uses com/flannel-io/flannel/pkg/trafficmngr✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel uses a type in com/flannel-io/flannel/pkg/trafficmngr.
- The types involved
github.com/flannel-io/flannel.main→github.com/flannel-io/flannel/pkg/trafficmngr.TrafficManager
- Direction
- com/flannel-io/flannel uses com/flannel-io/flannel/pkg/trafficmngr, so a change to com/flannel-io/flannel/pkg/trafficmngr can break com/flannel-io/flannel, while a change to com/flannel-io/flannel can't break com/flannel-io/flannel/pkg/trafficmngr.
- Position
- Below the diagonal: com/flannel-io/flannel uses a module listed above it, which is the healthy direction.
14→7 com/flannel-io/flannel/pkg/backend uses com/flannel-io/flannel/pkg/routing✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/backend uses a type in com/flannel-io/flannel/pkg/routing.
- The types involved
github.com/flannel-io/flannel/pkg/backend.RouteNetwork→github.com/flannel-io/flannel/pkg/routing.Route
- Direction
- com/flannel-io/flannel/pkg/backend uses com/flannel-io/flannel/pkg/routing, so a change to com/flannel-io/flannel/pkg/routing can break com/flannel-io/flannel/pkg/backend, while a change to com/flannel-io/flannel/pkg/backend can't break com/flannel-io/flannel/pkg/routing.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend uses a module listed above it, which is the healthy direction.
14→10 com/flannel-io/flannel/pkg/backend uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend.Network→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/backend.RouteNetwork→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/backend.SimpleNetwork→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/backend uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend, while a change to com/flannel-io/flannel/pkg/backend can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend uses a module listed above it, which is the healthy direction.
14→11 com/flannel-io/flannel/pkg/backend uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend.Backend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend.RouteNetwork→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend.backend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend.manager→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend, while a change to com/flannel-io/flannel/pkg/backend can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend uses a module listed above it, which is the healthy direction.
15→2 com/flannel-io/flannel/pkg/subnet/etcd uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 13 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet/etcd uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.MockSubnetRegistry→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.MockSubnetRegistry→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.Registry→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.Registry→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcdSubnetRegistry→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcdSubnetRegistry→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet/etcd.netwk→github.com/flannel-io/flannel/pkg/ip.IP4Net
- Direction
- com/flannel-io/flannel/pkg/subnet/etcd uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/subnet/etcd, while a change to com/flannel-io/flannel/pkg/subnet/etcd can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet/etcd uses a module listed above it, which is the healthy direction.
15→10 com/flannel-io/flannel/pkg/subnet/etcd uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 18 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet/etcd uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/lease.LeaseAttrsgithub.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResultgithub.com/flannel-io/flannel/pkg/subnet/etcd.MockSubnetRegistry→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/etcd.MockSubnetRegistry→github.com/flannel-io/flannel/pkg/lease.LeaseAttrsgithub.com/flannel-io/flannel/pkg/subnet/etcd.MockSubnetRegistry→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResultgithub.com/flannel-io/flannel/pkg/subnet/etcd.Registry→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/etcd.Registry→github.com/flannel-io/flannel/pkg/lease.LeaseAttrsgithub.com/flannel-io/flannel/pkg/subnet/etcd.Registry→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResultgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResultgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcdSubnetRegistry→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/etcd.etcdSubnetRegistry→github.com/flannel-io/flannel/pkg/lease.LeaseAttrsgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcdSubnetRegistry→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResultgithub.com/flannel-io/flannel/pkg/subnet/etcd.event→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/subnet/etcd.netwk→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/etcd.subnetWatch→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResult
- Direction
- com/flannel-io/flannel/pkg/subnet/etcd uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/subnet/etcd, while a change to com/flannel-io/flannel/pkg/subnet/etcd can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet/etcd uses a module listed above it, which is the healthy direction.
15→11 com/flannel-io/flannel/pkg/subnet/etcd uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet/etcd uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/subnet/etcd.LocalManager→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/subnet/etcd.etcd→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/subnet/etcd uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/subnet/etcd, while a change to com/flannel-io/flannel/pkg/subnet/etcd can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet/etcd uses a module listed above it, which is the healthy direction.
16→2 com/flannel-io/flannel/pkg/subnet/kube uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet/kube uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/subnet/kube.subnetFileInfo→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/subnet/kube.subnetFileInfo→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel/pkg/subnet/kube uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/subnet/kube, while a change to com/flannel-io/flannel/pkg/subnet/kube can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet/kube uses a module listed above it, which is the healthy direction.
16→10 com/flannel-io/flannel/pkg/subnet/kube uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 5 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet/kube uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/lease.EventTypegithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/lease.LeaseAttrsgithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/lease.LeaseWatchResult
- Direction
- com/flannel-io/flannel/pkg/subnet/kube uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/subnet/kube, while a change to com/flannel-io/flannel/pkg/subnet/kube can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet/kube uses a module listed above it, which is the healthy direction.
16→11 com/flannel-io/flannel/pkg/subnet/kube uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/subnet/kube uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/subnet/kube.kube→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/subnet/kube.kube→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/subnet/kube.kubeSubnetManager→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/subnet/kube uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/subnet/kube, while a change to com/flannel-io/flannel/pkg/subnet/kube can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/subnet/kube uses a module listed above it, which is the healthy direction.
17→2 com/flannel-io/flannel/pkg/trafficmngr/iptables uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel/pkg/trafficmngr/iptables uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr/iptables.IPTablesManager→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/trafficmngr/iptables.IPTablesManager→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel/pkg/trafficmngr/iptables uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/trafficmngr/iptables, while a change to com/flannel-io/flannel/pkg/trafficmngr/iptables can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr/iptables uses a module listed above it, which is the healthy direction.
17→10 com/flannel-io/flannel/pkg/trafficmngr/iptables uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/trafficmngr/iptables uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr/iptables.IPTablesManager→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/trafficmngr/iptables uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/trafficmngr/iptables, while a change to com/flannel-io/flannel/pkg/trafficmngr/iptables can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr/iptables uses a module listed above it, which is the healthy direction.
17→12 com/flannel-io/flannel/pkg/trafficmngr/iptables uses com/flannel-io/flannel/pkg/trafficmngr✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/trafficmngr/iptables uses a type in com/flannel-io/flannel/pkg/trafficmngr.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr/iptables.IPTablesManager→github.com/flannel-io/flannel/pkg/trafficmngr.IPTablesRulegithub.com/flannel-io/flannel/pkg/trafficmngr/iptables.IPTablesManager→github.com/flannel-io/flannel/pkg/trafficmngr.TrafficManagergithub.com/flannel-io/flannel/pkg/trafficmngr/iptables.iptables→github.com/flannel-io/flannel/pkg/trafficmngr.IPTablesRule
- Direction
- com/flannel-io/flannel/pkg/trafficmngr/iptables uses com/flannel-io/flannel/pkg/trafficmngr, so a change to com/flannel-io/flannel/pkg/trafficmngr can break com/flannel-io/flannel/pkg/trafficmngr/iptables, while a change to com/flannel-io/flannel/pkg/trafficmngr/iptables can't break com/flannel-io/flannel/pkg/trafficmngr.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr/iptables uses a module listed above it, which is the healthy direction.
18→2 com/flannel-io/flannel/pkg/trafficmngr/nftables uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel/pkg/trafficmngr/nftables uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr/nftables.NFTablesManager→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/trafficmngr/nftables.NFTablesManager→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel/pkg/trafficmngr/nftables uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/trafficmngr/nftables, while a change to com/flannel-io/flannel/pkg/trafficmngr/nftables can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr/nftables uses a module listed above it, which is the healthy direction.
18→10 com/flannel-io/flannel/pkg/trafficmngr/nftables uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/trafficmngr/nftables uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr/nftables.NFTablesManager→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/trafficmngr/nftables uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/trafficmngr/nftables, while a change to com/flannel-io/flannel/pkg/trafficmngr/nftables can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr/nftables uses a module listed above it, which is the healthy direction.
18→12 com/flannel-io/flannel/pkg/trafficmngr/nftables uses com/flannel-io/flannel/pkg/trafficmngr✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/trafficmngr/nftables uses a type in com/flannel-io/flannel/pkg/trafficmngr.
- The types involved
github.com/flannel-io/flannel/pkg/trafficmngr/nftables.NFTablesManager→github.com/flannel-io/flannel/pkg/trafficmngr.TrafficManager
- Direction
- com/flannel-io/flannel/pkg/trafficmngr/nftables uses com/flannel-io/flannel/pkg/trafficmngr, so a change to com/flannel-io/flannel/pkg/trafficmngr can break com/flannel-io/flannel/pkg/trafficmngr/nftables, while a change to com/flannel-io/flannel/pkg/trafficmngr/nftables can't break com/flannel-io/flannel/pkg/trafficmngr.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/trafficmngr/nftables uses a module listed above it, which is the healthy direction.
19→11 com/flannel-io/flannel/pkg/backend/alloc uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/alloc uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/alloc.AllocBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/alloc.AllocBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/alloc.alloc→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/alloc uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/alloc, while a change to com/flannel-io/flannel/pkg/backend/alloc can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/alloc uses a module listed above it, which is the healthy direction.
19→14 com/flannel-io/flannel/pkg/backend/alloc uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/alloc uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/alloc.AllocBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/alloc.AllocBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/alloc.alloc→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/alloc.alloc→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/alloc uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/alloc, while a change to com/flannel-io/flannel/pkg/backend/alloc can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/alloc uses a module listed above it, which is the healthy direction.
20→10 com/flannel-io/flannel/pkg/backend/extension uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/extension uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend/extension.network→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/backend/extension.network→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/backend/extension uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend/extension, while a change to com/flannel-io/flannel/pkg/backend/extension can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/extension uses a module listed above it, which is the healthy direction.
20→11 com/flannel-io/flannel/pkg/backend/extension uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/extension uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/extension.ExtensionBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/extension.ExtensionBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/extension.extension→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/extension.network→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/extension uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/extension, while a change to com/flannel-io/flannel/pkg/backend/extension can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/extension uses a module listed above it, which is the healthy direction.
20→14 com/flannel-io/flannel/pkg/backend/extension uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 6 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/extension uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/extension.ExtensionBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/extension.ExtensionBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/extension.extension→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/extension.extension→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/extension.network→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/extension.network→github.com/flannel-io/flannel/pkg/backend.Network
- Direction
- com/flannel-io/flannel/pkg/backend/extension uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/extension, while a change to com/flannel-io/flannel/pkg/backend/extension can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/extension uses a module listed above it, which is the healthy direction.
21→11 com/flannel-io/flannel/pkg/backend/hostgw uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/hostgw uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/hostgw.HostgwBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/hostgw.HostgwBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/hostgw.hostgw→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/hostgw uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/hostgw, while a change to com/flannel-io/flannel/pkg/backend/hostgw can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/hostgw uses a module listed above it, which is the healthy direction.
21→14 com/flannel-io/flannel/pkg/backend/hostgw uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/hostgw uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/hostgw.HostgwBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/hostgw.HostgwBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/hostgw.hostgw→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/hostgw.hostgw→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/hostgw uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/hostgw, while a change to com/flannel-io/flannel/pkg/backend/hostgw can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/hostgw uses a module listed above it, which is the healthy direction.
22→2 com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/backend/ipip uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipip.IPIPBackend→github.com/flannel-io/flannel/pkg/ip.IP4Net
- Direction
- com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/backend/ipip, while a change to com/flannel-io/flannel/pkg/backend/ipip can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipip uses a module listed above it, which is the healthy direction.
22→10 com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/backend/ipip uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipip.IPIPBackend→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend/ipip, while a change to com/flannel-io/flannel/pkg/backend/ipip can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipip uses a module listed above it, which is the healthy direction.
22→11 com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/ipip uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipip.IPIPBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/ipip.IPIPBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/ipip.ipip→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/ipip, while a change to com/flannel-io/flannel/pkg/backend/ipip can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipip uses a module listed above it, which is the healthy direction.
22→14 com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/ipip uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipip.IPIPBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/ipip.IPIPBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/ipip.ipip→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/ipip.ipip→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/ipip uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/ipip, while a change to com/flannel-io/flannel/pkg/backend/ipip can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipip uses a module listed above it, which is the healthy direction.
23→10 com/flannel-io/flannel/pkg/backend/ipsec uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/ipsec uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipsec.CharonIKEDaemon→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/backend/ipsec.ipsec→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/backend/ipsec.network→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/backend/ipsec.network→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/backend/ipsec uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend/ipsec, while a change to com/flannel-io/flannel/pkg/backend/ipsec can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipsec uses a module listed above it, which is the healthy direction.
23→11 com/flannel-io/flannel/pkg/backend/ipsec uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/ipsec uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipsec.IPSECBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/ipsec.IPSECBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/ipsec.ipsec→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/ipsec.network→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/ipsec uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/ipsec, while a change to com/flannel-io/flannel/pkg/backend/ipsec can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipsec uses a module listed above it, which is the healthy direction.
23→14 com/flannel-io/flannel/pkg/backend/ipsec uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 5 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/ipsec uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/ipsec.IPSECBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/ipsec.IPSECBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/ipsec.ipsec→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/ipsec.ipsec→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/ipsec.network→github.com/flannel-io/flannel/pkg/backend.Network
- Direction
- com/flannel-io/flannel/pkg/backend/ipsec uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/ipsec, while a change to com/flannel-io/flannel/pkg/backend/ipsec can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/ipsec uses a module listed above it, which is the healthy direction.
24→11 com/flannel-io/flannel/pkg/backend/tencentvpc uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/tencentvpc uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/tencentvpc.TencentVpcBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/tencentvpc.TencentVpcBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/tencentvpc.tencentvpc→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/tencentvpc uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/tencentvpc, while a change to com/flannel-io/flannel/pkg/backend/tencentvpc can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/tencentvpc uses a module listed above it, which is the healthy direction.
24→14 com/flannel-io/flannel/pkg/backend/tencentvpc uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/tencentvpc uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/tencentvpc.TencentVpcBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/tencentvpc.TencentVpcBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/tencentvpc.tencentvpc→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/tencentvpc.tencentvpc→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/tencentvpc uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/tencentvpc, while a change to com/flannel-io/flannel/pkg/backend/tencentvpc can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/tencentvpc uses a module listed above it, which is the healthy direction.
25→2 com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/udp uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/backend/udp.network→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/backend/udp.udp→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/backend/udp.udp→github.com/flannel-io/flannel/pkg/ip.IP4Net
- Direction
- com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/backend/udp, while a change to com/flannel-io/flannel/pkg/backend/udp can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/udp uses a module listed above it, which is the healthy direction.
25→10 com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 2 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/udp uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend/udp.network→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/backend/udp.udp→github.com/flannel-io/flannel/pkg/lease.Lease
- Direction
- com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend/udp, while a change to com/flannel-io/flannel/pkg/backend/udp can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/udp uses a module listed above it, which is the healthy direction.
25→11 com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/udp uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/udp.UdpBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/udp.UdpBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/udp.network→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/udp.udp→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/udp, while a change to com/flannel-io/flannel/pkg/backend/udp can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/udp uses a module listed above it, which is the healthy direction.
25→14 com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 5 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/udp uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/udp.UdpBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/udp.UdpBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/udp.network→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/udp.udp→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/udp.udp→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/udp uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/udp, while a change to com/flannel-io/flannel/pkg/backend/udp can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/udp uses a module listed above it, which is the healthy direction.
26→2 com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 6 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/vxlan uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/backend/vxlan.neighbor→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/backend/vxlan.neighbor→github.com/flannel-io/flannel/pkg/ip.IP6github.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlanDevice→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlanDevice→github.com/flannel-io/flannel/pkg/ip.IP6Netgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlanDeviceAttrs→github.com/flannel-io/flannel/pkg/ip.IP4Net
- Direction
- com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/backend/vxlan, while a change to com/flannel-io/flannel/pkg/backend/vxlan can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/vxlan uses a module listed above it, which is the healthy direction.
26→10 com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 3 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/vxlan uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend/vxlan.network→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/lease.LeaseAttrs
- Direction
- com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend/vxlan, while a change to com/flannel-io/flannel/pkg/backend/vxlan can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/vxlan uses a module listed above it, which is the healthy direction.
26→11 com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 5 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/vxlan uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/vxlan.VXLANBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/vxlan.VXLANBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/vxlan.network→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/vxlan, while a change to com/flannel-io/flannel/pkg/backend/vxlan can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/vxlan uses a module listed above it, which is the healthy direction.
26→14 com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 5 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/vxlan uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/vxlan.VXLANBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/vxlan.VXLANBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/vxlan.network→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/vxlan.vxlan→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/vxlan uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/vxlan, while a change to com/flannel-io/flannel/pkg/backend/vxlan can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/vxlan uses a module listed above it, which is the healthy direction.
27→2 com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/ip✕
- Connections
- 6 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/wireguard uses a type in com/flannel-io/flannel/pkg/ip.
- The types involved
github.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/ip.IP6github.com/flannel-io/flannel/pkg/backend/wireguard.wgDevice→github.com/flannel-io/flannel/pkg/ip.IP4github.com/flannel-io/flannel/pkg/backend/wireguard.wgDevice→github.com/flannel-io/flannel/pkg/ip.IP4Netgithub.com/flannel-io/flannel/pkg/backend/wireguard.wgDevice→github.com/flannel-io/flannel/pkg/ip.IP6github.com/flannel-io/flannel/pkg/backend/wireguard.wgDevice→github.com/flannel-io/flannel/pkg/ip.IP6Net
- Direction
- com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/ip, so a change to com/flannel-io/flannel/pkg/ip can break com/flannel-io/flannel/pkg/backend/wireguard, while a change to com/flannel-io/flannel/pkg/backend/wireguard can't break com/flannel-io/flannel/pkg/ip.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/wireguard uses a module listed above it, which is the healthy direction.
27→10 com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/lease✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/wireguard uses a type in com/flannel-io/flannel/pkg/lease.
- The types involved
github.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/lease.Eventgithub.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/backend/wireguard.wireguard→github.com/flannel-io/flannel/pkg/lease.Leasegithub.com/flannel-io/flannel/pkg/backend/wireguard.wireguard→github.com/flannel-io/flannel/pkg/lease.LeaseAttrs
- Direction
- com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/lease, so a change to com/flannel-io/flannel/pkg/lease can break com/flannel-io/flannel/pkg/backend/wireguard, while a change to com/flannel-io/flannel/pkg/backend/wireguard can't break com/flannel-io/flannel/pkg/lease.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/wireguard uses a module listed above it, which is the healthy direction.
27→11 com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/subnet✕
- Connections
- 4 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/wireguard uses a type in com/flannel-io/flannel/pkg/subnet.
- The types involved
github.com/flannel-io/flannel/pkg/backend/wireguard.WireguardBackend→github.com/flannel-io/flannel/pkg/subnet.Configgithub.com/flannel-io/flannel/pkg/backend/wireguard.WireguardBackend→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/subnet.Managergithub.com/flannel-io/flannel/pkg/backend/wireguard.wireguard→github.com/flannel-io/flannel/pkg/subnet.Manager
- Direction
- com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/subnet, so a change to com/flannel-io/flannel/pkg/subnet can break com/flannel-io/flannel/pkg/backend/wireguard, while a change to com/flannel-io/flannel/pkg/backend/wireguard can't break com/flannel-io/flannel/pkg/subnet.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/wireguard uses a module listed above it, which is the healthy direction.
27→14 com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 6 pairs of types, where a type in com/flannel-io/flannel/pkg/backend/wireguard uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/backend/wireguard.WireguardBackend→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/wireguard.WireguardBackend→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/backend.ExternalInterfacegithub.com/flannel-io/flannel/pkg/backend/wireguard.network→github.com/flannel-io/flannel/pkg/backend.Networkgithub.com/flannel-io/flannel/pkg/backend/wireguard.wireguard→github.com/flannel-io/flannel/pkg/backend.Backendgithub.com/flannel-io/flannel/pkg/backend/wireguard.wireguard→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/backend/wireguard uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/backend/wireguard, while a change to com/flannel-io/flannel/pkg/backend/wireguard can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/backend/wireguard uses a module listed above it, which is the healthy direction.
28→14 com/flannel-io/flannel/pkg/ipmatch uses com/flannel-io/flannel/pkg/backend✕
- Connections
- 1 pair of types, where a type in com/flannel-io/flannel/pkg/ipmatch uses a type in com/flannel-io/flannel/pkg/backend.
- The types involved
github.com/flannel-io/flannel/pkg/ipmatch.ipmatch→github.com/flannel-io/flannel/pkg/backend.ExternalInterface
- Direction
- com/flannel-io/flannel/pkg/ipmatch uses com/flannel-io/flannel/pkg/backend, so a change to com/flannel-io/flannel/pkg/backend can break com/flannel-io/flannel/pkg/ipmatch, while a change to com/flannel-io/flannel/pkg/ipmatch can't break com/flannel-io/flannel/pkg/backend.
- Position
- Below the diagonal: com/flannel-io/flannel/pkg/ipmatch 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 |
|---|---|---|
| A02:2025 — Security Misconfiguration | 114 | High / Critical |
| A05:2025 — Injection | 14 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 37 Low coverage finding(s) in Code Coverage — start with REDACTED (2), device.go (2), utils.go (2); Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail; Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +3.0 pts | Low | Dependency Hygiene |
| Resolve the 37 Low coverage finding(s) in Code Coverage — start with REDACTED (2), device.go (2), utils.go (2). | +5.6 pts | Medium | Code Coverage |
| Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail. | +3.7 pts | Medium | Outbound HTTP resilience |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.9 pts | Medium | Release Hygiene |
| Resolve the 1 ADR Decision section is empty finding(s) in ADR Quality — start with add-nftables-implementation.md. | +0.7 pts | Low | ADR Quality |
| Resolve the 1 ADR has no Consequences section finding(s) in ADR Quality — start with add-nftables-implementation.md. | +0.7 pts | Low | ADR Quality |
| Resolve the 1 No network policy finding(s) in Network Egress Confinement. | +0.7 pts | Low | Network Egress Confinement |
| Resolve the 3 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2), REDACTED. | +0.7 pts | Low | Kernel & Syscall Confinement |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| pkg/trafficmngr/iptables/iptables.go | 5.5 | Mixed | Cognitive Complexity: iptables.ipTablesCleanAndBuild (cognitive 33) |
| pkg/ip/iface.go | 5.5 | Mixed | Cognitive Complexity: ip.EnsureV6AddressOnLink (cognitive 16) |
| pkg/backend/vxlan/vxlan_network.go | 5.6 | Mixed | Cyclomatic Complexity: network.handleSubnetEvents (cyclomatic 47) |
| pkg/backend/vxlan/device.go | 5.6 | Mixed | Cyclomatic Complexity: vxlan.vxlanLinksIncompat (cyclomatic 17) |
| pkg/backend/extension/extension_network.go | 5.6 | Mixed | Cognitive Complexity: network.handleSubnetEvents (cognitive 43) |
| pkg/backend/route_network.go | 5.6 | Mixed | Cognitive Complexity: RouteNetwork.handleSubnetEvents (cognitive 29) |
| REDACTED | 5.6 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| pkg/backend/wireguard/wireguard_network.go | 5.7 | Mixed | Cyclomatic Complexity: network.handleSubnetEvents (cyclomatic 46) |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| pkg/ipmatch/match.go | 5.9 | Mixed | Cyclomatic Complexity: ipmatch.LookupExtIface (cyclomatic 79) |
| pkg/backend/tencentvpc/tencentvpc.go | 5.9 | Mixed | Cyclomatic Complexity: TencentVpcBackend.RegisterNetwork (cyclomatic 23) |
| pkg/backend/ipsec/ipsec_network.go | 5.9 | Mixed | Cognitive Complexity: network.handleSubnetEvents (cognitive 30) |
| pkg/trafficmngr/nftables/nftables.go | 5.9 | Mixed | Code Duplication: Edited copy of a member (53 corresponding lines) |
| pkg/backend/wireguard/device.go | 5.9 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| pkg/subnet/kube/kube.go | 6.0 | Mixed | Explicit Debt: TodoComment |
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 50 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 50 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, 294 of 313 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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.
- D26 Project Cohesion — 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. `(repository root)` (10867 LoC, 79 module-visible types across 28 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D34 Knowledge Freshness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. File-level freshness contradicts repo activity: 42 commits in the last 90 days, yet 34 of 42 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- D41 Kernel & Syscall Confinement — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Chart/kube-flannel/templates/daemonset.yaml:2 did not read as a pod spec (a templated manifest such as Helm's that is not YAML until rendered, or a workload whose pod spec this check does not locate), so the seccomp/AppArmor profile in force there was not judged and no row about them can appear on this card.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Go, c 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 Go, c is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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 and Rust source only, and no C# was loaded and no JavaScript/TypeScript, 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.
- 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.
- X16 Unfloored truncation loop — 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, PHP, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, 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.
- 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, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, 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.
- X18 Disposal-pattern 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, Java, Kotlin, Dart, Ruby, Scala, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP 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.
- X22 Contradicted release guard — 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# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's C, Go 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.
- X23 Unguarded diagnostic materialisation — 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, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP 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.
- X25 Inert configuration knob — 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, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby 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.
- X29 Per-element action decided by a fixed element — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala 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.
- X5 Nullable reference types — 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's C 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.
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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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.
- D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
- D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
- D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
16 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was ipmatch.LookupExtIface at 79.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with ipmatch.LookupExtIface (cyclomatic 79), kubeSubnetManager.AcquireLease (cyclomatic 65), main.main (cyclomatic 57). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 5.8 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
28 function(s) exceeded the cognitive complexity threshold of 15; the worst was network.handleSubnetEvents at 187.
What to do
- Bring the 11 bodies over 30 down to 30 or less in Cognitive Complexity — start with network.handleSubnetEvents (cognitive 187), ipmatch.LookupExtIface (cognitive 183), network.handleSubnetEvents (cognitive 154). — 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 11 together lifts Cognitive Complexity from 2.0 to about 5.9/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
5 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 3 MethodTooLong finding(s) in God Classes — start with vxlan_network.go, kube.go, wireguard_network.go. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with REDACTED, match.go. — One of this dimension's main actionable groups (2 warning-level).
D4 · Code Duplication
29 duplicated block group(s) detected. 11.5 % of the production lines (1,250 of 10,867) are in a reported copy. A further 21 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 4 Edited copy of a member (22 corresponding lines) finding(s) in Code Duplication — start with device.go, REDACTED, extension_network.go. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with route_network.go, vxlan_network.go, iface.go. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with extension_network.go, iptables.go, ip6net.go. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
0 of 21 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D8 · Code Coverage
Line coverage 19.4% — 37 file(s) below 50%. Measured from the Go suite (github.com/flannel-io/flannel: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 2 line(s) in 1 file(s) were executed in some runs and not in others, so they are not counted.
What to do
- Resolve the 37 Low coverage finding(s) in Code Coverage — start with REDACTED (2), device.go (2), utils.go (2). — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 1 Tests reach code only in some runs finding(s) in Code Coverage — start with registry.go. — One of this dimension's main actionable groups (1 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/flannel-io/flannel): measured (0 flaky).
D12 · Dependency Hygiene
12 outdated, 0 author-deprecated direct Go module(s), 1 pinning or checksum defect(s). 30 of 30 direct requirement(s) were graded against proxy.golang.org (0 not served there, 3 publishing no tagged release to be behind). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
What to do
- Resolve the 1 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 144 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is pkg/backend/extension/extension.go. Counted over 41 of the 71 production source files in this repository: 29 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
7 deducted task-comment markers across 10867 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with mock_registry.go (3), kube.go (2), registry_test.go. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 16 document(s) read across 1 unit(s).
D20 · ADR Quality
1 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
What to do
- Resolve the 1 ADR Decision section is empty finding(s) in ADR Quality — start with add-nftables-implementation.md. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 ADR has no Consequences section finding(s) in ADR Quality — start with add-nftables-implementation.md. — One of this dimension's main actionable groups (1 recommendation-level).
D22 · Internal API Consistency
1 API inconsistencies among 38 exposed members measured against a convention their peers follow.
What to do
- Resolve the 1 `Manager.HandleSubnetFile` takes no context.Context; its 6 sibling… finding(s) in Internal API Consistency — start with subnet.go. — One of this dimension's main actionable groups (1 warning-level).
D27 · Navigability
49 % of calls cross a namespace and 7 % go through an interface, but 33 % 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)
15 finding(s): 0 critical, 3 high, 7 medium, 5 low. semgrep hit a parse error in 3 file(s) — `chart/kube-flannel/templates/config.yaml`, `REDACTED`, `chart/kube-flannel/templates/rbac.yaml` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 0 high, 3 medium, 0 low.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
114 finding(s): 0 critical, 15 high, 74 medium, 25 low.
What to do
- Resolve the 74 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (34), REDACTED (26), REDACTED (14). — One of this dimension's main actionable groups (74 warning-level).
- Resolve the 25 Low IaC finding(s) in IaC & Container Security — start with REDACTED (11), REDACTED (8), REDACTED (5). — One of this dimension's main actionable groups (25 recommendation-level).
- Resolve the 15 High IaC finding(s) in IaC & Container Security — start with REDACTED (5), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (15 issue-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D40 · Network Egress Confinement
0/2 network-egress controls present (network policy, egress restriction).
What to do
- Resolve the 1 No network policy finding(s) in Network Egress Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
D41 · Kernel & Syscall Confinement
0/3 workload(s) run every container under a seccomp profile; 0/3 declare an AppArmor/SELinux profile.
What to do
- Resolve the 3 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
D42 · Runtime Threat Enforcement
1/2 runtime-enforcement controls present (threat detection, admission control).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 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
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — pkg/backend/tencentvpc/tencentvpc.go:56
What to do
- Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
X14 · Bypassable address classification
X2 · Cancellation propagation
- Only 1/2 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `get_vm_metadata` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — pkg/backend/tencentvpc/tencentvpc.go:55
What to do
- Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `if _, err := os.Stat(tempFilePath); err == nil` reports `err` on the one path where it is nil, and the path where the call failed goes on without ever reading it: the comparison is inverted. The real failure is lost and a nil error (or a panic on `err.Error()`) is reported in its place. Test `err != nil` here. — pkg/utils/utils.go:29
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — pkg/routing/router_windows.go:70, pkg/backend/vxlan/device_windows.go:188
- `nerr, ok := err.(net.Error)` failed on this branch, so `nerr` is the zero value of `net.Error` here, and that is what is reported: the value that did not fit is lost. Report `err` itself (and `%T` of it) instead. — pkg/backend/route_network.go:250
- `existingRoutes, _ := router.GetRoutesFromInterfaceToSubnet(expectedRoute.InterfaceIndex, expectedRoute.DestinationSubnet)` writes the call's error to `_` and then uses `existingRoutes` as if the call succeeded. When `router.GetRoutesFromInterfaceToSubnet` fails, `existingRoutes` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `existingRoutes` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×2) — pkg/backend/route_network_windows.go:97, pkg/backend/route_network_windows.go:123
- `addNetAdapterName(network, devAttrs.interfaceName)` returns an error, and the statement drops it: when `addNetAdapterName` fails nothing records it and the code after it runs as if it had succeeded. Check it (`if err := addNetAdapterName(network, devAttrs.interfaceName); err != nil { … }`) and return or log it with what was being done, or assign it to `_` with a comment saying why the failure cannot matter. — pkg/backend/vxlan/device_windows.go:91
What to do
- Lost error (reports an error that is nil on this path)
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69.6 | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94.3 | Exemplary | Strongest area. |
| Maturity | 88.1 | Strong | Solid. |
| Readiness | 63.0 | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68.2 | Adequate — gated by D29, D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · 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'.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 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 Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — This repository has no user interface to render — no markup (HTML, Razor, JSX, Vue, Svelte or server templates), no UI framework dependency, no UI component source and no native UI project — so WCAG's runtime success criteria have nothing to apply to here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~5902 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1637 declarations, no unit with a dominant convention).
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
- 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
- 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 data present for 50 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, 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: Go 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X16 Unfloored truncation loop — 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
- 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 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
- 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
- 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.
- X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. In C a `case` label must be a constant expression, and a switch has no guards, so no label can change state. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- 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
- X25 Inert configuration knob — 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
- X29 Per-element action decided by a fixed element — 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
- X5 Nullable reference types — 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 240 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
- Low coverage: cmd/install_conf/REDACTED cmd/install_conf/REDACTED:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: pkg/backend/alloc/alloc.go pkg/backend/alloc/alloc.go:1
- Low coverage: pkg/backend/extension/extension.go pkg/backend/extension/extension.go:1
- Low coverage: pkg/backend/extension/extension_network.go pkg/backend/extension/extension_network.go:1
- Low coverage: pkg/backend/hostgw/hostgw.go pkg/backend/hostgw/hostgw.go:1
- Low coverage: pkg/backend/ipip/ipip.go pkg/backend/ipip/ipip.go:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: pkg/backend/ipsec/handle_xfrm.go pkg/backend/ipsec/handle_xfrm.go:1
- Low coverage: pkg/backend/ipsec/ipsec.go pkg/backend/ipsec/ipsec.go:1
- Low coverage: pkg/backend/ipsec/ipsec_network.go pkg/backend/ipsec/ipsec_network.go:1
- Low coverage: pkg/backend/manager.go pkg/backend/manager.go:1
- Low coverage: pkg/backend/route_network.go pkg/backend/route_network.go:1
- Low coverage: pkg/backend/simple_network.go pkg/backend/simple_network.go:1
- Low coverage: pkg/backend/tencentvpc/tencentvpc.go pkg/backend/tencentvpc/tencentvpc.go:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: pkg/backend/udp/udp_amd64.go pkg/backend/udp/udp_amd64.go:1
- Low coverage: pkg/backend/udp/udp_network_amd64.go pkg/backend/udp/udp_network_amd64.go:1
- Low coverage: pkg/backend/vxlan/device.go pkg/backend/vxlan/device.go:1
- Low coverage: pkg/backend/vxlan/vxlan.go pkg/backend/vxlan/vxlan.go:1
- Low coverage: pkg/backend/vxlan/vxlan_network.go pkg/backend/vxlan/vxlan_network.go:1
- Low coverage: pkg/backend/wireguard/device.go pkg/backend/wireguard/device.go:1
- Low coverage: pkg/backend/wireguard/wireguard.go pkg/backend/wireguard/wireguard.go:1
- Low coverage: pkg/backend/wireguard/wireguard_network.go pkg/backend/wireguard/wireguard_network.go:1
- Low coverage: pkg/ip/iface.go pkg/ip/iface.go:1
- TodoComment pkg/subnet/kube/kube.go:433
- TodoComment pkg/subnet/kube/kube.go:512
- TodoComment pkg/subnet/etcd/mock_registry.go:97
- TodoComment pkg/subnet/etcd/mock_registry.go:145
- TodoComment pkg/subnet/etcd/mock_registry.go:226
- TodoComment pkg/subnet/etcd/registry_test.go:292
- TodoComment pkg/backend/manager.go:76
- Edited copy of a member (22 corresponding lines) pkg/backend/vxlan/device.go:129
- Edited copy of a member (22 corresponding lines) REDACTED:620
- Edited copy of a member (22 corresponding lines) pkg/backend/extension/extension_network.go:48
- Edited copy of a member (22 corresponding lines) pkg/subnet/etcd/local_manager.go:316
- Duplicated block (9 lines × 2) pkg/backend/route_network.go:54
- Duplicated block (9 lines × 2) pkg/backend/vxlan/vxlan_network.go:362
- Duplicated block (9 lines × 2) pkg/ip/iface.go:67
- Duplicated block (9 lines × 2) pkg/backend/ipsec/ipsec_network.go:114
- Duplicated block (7 lines × 2) pkg/backend/extension/extension_network.go:93
- Duplicated block (7 lines × 2) pkg/trafficmngr/iptables/iptables.go:31
- Duplicated block (7 lines × 2) pkg/ip/ip6net.go:137
- Duplicated block (7 lines × 2) pkg/subnet/kube/kube.go:560
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: network.handleSubnetEvents pkg/backend/vxlan/vxlan_network.go:335
- MethodTooLong: kubeSubnetManager.AcquireLease pkg/subnet/kube/kube.go:350
- MethodTooLong: network.handleSubnetEvents pkg/backend/wireguard/wireguard_network.go:131
- Duplicated block (14 lines × 2) pkg/backend/tencentvpc/tencentvpc.go:111
- Duplicated block (14 lines × 2) pkg/backend/vxlan/vxlan.go:284
- Duplicated block (14 lines × 2) pkg/trafficmngr/nftables/nftables.go:83
- FunctionTooLong: main.main REDACTED:217
- FunctionTooLong: ipmatch.LookupExtIface pkg/ipmatch/match.go:53
- REDACTED
- REDACTED
- Edited copy of a member (10 corresponding lines) pkg/backend/vxlan/device.go:209
- Edited copy of a member (10 corresponding lines) pkg/backend/route_network.go:212
- Duplicated block (12 lines × 2) pkg/trafficmngr/nftables/nftables.go:158
- Duplicated block (12 lines × 2) REDACTED:119
- Duplicated block (10 lines × 2) pkg/backend/wireguard/device.go:255
- Duplicated block (10 lines × 2) pkg/subnet/etcd/registry.go:222
- Duplicated block (8 lines × 2) pkg/backend/extension/extension_network.go:83
- Duplicated block (8 lines × 2) pkg/backend/wireguard/wireguard_network.go:190
- Duplicated block (6 lines × 2) REDACTED:622
- Duplicated block (6 lines × 2) pkg/ip/ip6net.go:173
- Duplicated block (11 lines × 2) pkg/backend/hostgw/hostgw.go:41
- Duplicated block (11 lines × 2) pkg/subnet/etcd/registry.go:615
- Swallowed exception (caught, then discarded) pkg/routing/router_windows.go:70
- Swallowed exception (caught, then discarded) pkg/backend/vxlan/device_windows.go:188
- Discarded error (assigned to `_`, then its result used) pkg/backend/route_network_windows.go:97
- Discarded error (assigned to `_`, then its result used) pkg/backend/route_network_windows.go:123
- ipmatch.LookupExtIface (cyclomatic 79) pkg/ipmatch/match.go:53
- kubeSubnetManager.AcquireLease (cyclomatic 65) pkg/subnet/kube/kube.go:350
- main.main (cyclomatic 57) REDACTED:217
- network.handleSubnetEvents (cyclomatic 47) pkg/backend/vxlan/vxlan_network.go:335
- network.handleSubnetEvents (cyclomatic 46) pkg/backend/wireguard/wireguard_network.go:131
- subnet.CheckNetworkConfig (cyclomatic 27) pkg/subnet/config.go:76
- etcdSubnetRegistry.runWatch (cyclomatic 24) pkg/subnet/etcd/registry.go:300
- TencentVpcBackend.RegisterNetwork (cyclomatic 23) pkg/backend/tencentvpc/tencentvpc.go:96
- kubeSubnetManager.nodeToLease (cyclomatic 21) pkg/subnet/kube/kube.go:542
- WireguardBackend.RegisterNetwork (cyclomatic 20) pkg/backend/wireguard/wireguard.go:113
- IPIPBackend.configureIPIPDevice (cyclomatic 18) pkg/backend/ipip/ipip.go:128
- vxlan.vxlanLinksIncompat (cyclomatic 17) pkg/backend/vxlan/device.go:275
- vxlan.ensureNetwork (cyclomatic 16) pkg/backend/vxlan/device_windows.go:104
- LocalManager.tryAcquireLease (cyclomatic 16) pkg/subnet/etcd/local_manager.go:148
- LocalManager.allocateSubnet (cyclomatic 16) pkg/subnet/etcd/local_manager.go:225
- kube.NewSubnetManager (cyclomatic 16) pkg/subnet/kube/kube.go:81
- Dependency pinned to a stale untagged commit: golang.zx2c4.com/wireguard/wgctrl
- network.handleSubnetEvents (cognitive 187) pkg/backend/vxlan/vxlan_network.go:335
- ipmatch.LookupExtIface (cognitive 183) pkg/ipmatch/match.go:53
- network.handleSubnetEvents (cognitive 154) pkg/backend/wireguard/wireguard_network.go:131
- main.main (cognitive 106) REDACTED:217
- etcdSubnetRegistry.runWatch (cognitive 86) pkg/subnet/etcd/registry.go:300
- kubeSubnetManager.AcquireLease (cognitive 83) pkg/subnet/kube/kube.go:350
- subnet.CheckNetworkConfig (cognitive 54) pkg/subnet/config.go:76
- kubeSubnetManager.nodeToLease (cognitive 48) pkg/subnet/kube/kube.go:542
- network.handleSubnetEvents (cognitive 43) pkg/backend/extension/extension_network.go:71
- iptables.ipTablesCleanAndBuild (cognitive 33) pkg/trafficmngr/iptables/iptables.go:296
- WireguardBackend.RegisterNetwork (cognitive 31) pkg/backend/wireguard/wireguard.go:113
- network.handleSubnetEvents (cognitive 30) pkg/backend/ipsec/ipsec_network.go:108
- RouteNetwork.handleSubnetEvents (cognitive 29) pkg/backend/route_network.go:83
- TencentVpcBackend.RegisterNetwork (cognitive 29) pkg/backend/tencentvpc/tencentvpc.go:96
- network.reCreateVxlan (cognitive 29) pkg/backend/vxlan/vxlan_network.go:224
- RouteNetwork.checkSubnetExistInRoutes (cognitive 28) pkg/backend/route_network.go:232
- vxlan.ensureNetwork (cognitive 28) pkg/backend/vxlan/device_windows.go:104
- LocalManager.allocateSubnet (cognitive 28) pkg/subnet/etcd/local_manager.go:225
- LocalManager.tryAcquireLease (cognitive 27) pkg/subnet/etcd/local_manager.go:148
- IPIPBackend.configureIPIPDevice (cognitive 26) pkg/backend/ipip/ipip.go:128
- iptables.teardownIPTables (cognitive 26) pkg/trafficmngr/iptables/iptables.go:502
- network.watchVXLANDeviceWithSubscriber (cognitive 24) pkg/backend/vxlan/vxlan_network.go:125
- iptables.ipTablesRulesExist (cognitive 22) pkg/trafficmngr/iptables/iptables.go:263
- kube.NewSubnetManager (cognitive 19) pkg/subnet/kube/kube.go:81
- ExtensionBackend.RegisterNetwork (cognitive 18) pkg/backend/extension/extension.go:58
- iptables.buildIPTablesRestorePayload (cognitive 17) pkg/trafficmngr/iptables/iptables_restore.go:124
- ip.EnsureV6AddressOnLink (cognitive 16) pkg/ip/iface.go:279
- kube.newKubeSubnetManager (cognitive 16) pkg/subnet/kube/kube.go:171
- `Manager.HandleSubnetFile` takes no context.Context; its 6 sibling operations take one pkg/subnet/subnet.go:96
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (35 corresponding lines) pkg/trafficmngr/iptables/iptables.go:135
- Edited copy of a member (53 corresponding lines) pkg/trafficmngr/nftables/nftables.go:78
- Edited copy of a member (44 corresponding lines) pkg/trafficmngr/iptables/iptables.go:296
- Edited copy of a member (31 corresponding lines) pkg/ip/iface.go:245
- Edited copy of a member (36 corresponding lines) pkg/trafficmngr/iptables/iptables.go:363
- Edited copy of a member (27 corresponding lines) pkg/ip/iface.go:52
- Edited copies of one member (3 members, 25+ corresponding lines) pkg/backend/route_network.go:53
- Edited copy of a member (17 corresponding lines) pkg/ip/iface.go:146
- Edited copy of a member (12 corresponding lines) REDACTED:607
- Edited copy of a member (13 corresponding lines) pkg/backend/wireguard/device.go:252
- Edited copy of a member (20 corresponding lines) pkg/trafficmngr/iptables/iptables.go:438
- Edited copy of a member (8 corresponding lines) pkg/ip/iface.go:315
- Edited copies of one member (6 members, 10+ corresponding lines) pkg/backend/vxlan/device.go:185
- Edited copy of a member (18 corresponding lines) pkg/ip/iface.go:108
- Edited copies of one member (3 members, 12+ corresponding lines) pkg/backend/ipsec/ipsec_network.go:60
- Duplicated block (16 lines × 2) pkg/backend/wireguard/device.go:303
- Duplicated block (14–15 lines × 2) pkg/backend/vxlan/vxlan.go:206
- Duplicated block (15 lines × 2) pkg/trafficmngr/iptables/iptables.go:384
- Duplicated block (13 lines × 2) pkg/backend/extension/extension_network.go:49
- Duplicated block (8–10 lines × 2) pkg/subnet/kube/kube.go:701
- Duplicated block (18–20 lines × 2) pkg/trafficmngr/iptables/iptables.go:140
- Duplicated block (5 lines × 2) pkg/trafficmngr/iptables/iptables.go:165
- Duplicated block (17 lines × 2) pkg/backend/vxlan/device.go:134
- Test failure does not fail the CI gate .github/workflows/e2eTests.yaml:27
- Outbound HTTP without resilience pkg/backend/tencentvpc/tencentvpc.go:56
- Function without context.Context: get_vm_metadata pkg/backend/tencentvpc/tencentvpc.go:55
- Lost error (reports an error that is nil on this path) pkg/utils/utils.go:29
- Lost error (reports the zero value of a failed type assertion) pkg/backend/route_network.go:250
- Discarded error (an error-returning call as a bare statement) pkg/backend/vxlan/device_windows.go:91
Minor — 43 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No seccomp profile REDACTED:101
- No seccomp profile REDACTED:93
- No seccomp profile REDACTED:39
- Off-boarding risk: anonymized user #1
- ADR Decision section is empty Documentation/adrs/add-nftables-implementation.md:91
- ADR has no Consequences section Documentation/adrs/add-nftables-implementation.md:1
- Scattered collaborators
- REDACTED
- No network policy
- Tests reach code only in some runs: pkg/subnet/etcd/registry.go pkg/subnet/etcd/registry.go:375
- No changelog
- Duplicated predicate pkg/backend/vxlan/vxlan.go:284
- Not all functions that make a request accept a context.Context
- Silent fallback default on error pkg/backend/vxlan/device_windows.go:188
Minor — 12 finding(s)
- Outdated: github.com/avast/retry-go/v5
- Outdated: github.com/containernetworking/plugins
- Outdated: github.com/onsi/ginkgo/v2
- Outdated: github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common
- Outdated: github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/vpc
- Outdated: golang.org/x/sync
- Outdated: golang.org/x/sys
- Outdated: k8s.io/api
- Outdated: k8s.io/apimachinery
- Outdated: k8s.io/client-go
- Outdated: sigs.k8s.io/kind
- Outdated: sigs.k8s.io/knftables
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-af26638efd8f440cbe1851f4e087b106/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-af26638efd8f440cbe1851f4e087b106/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=1190" --report-format json --report-path /tmp/watchdog-gitleaks-af26638efd8f440cbe1851f4e087b106/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-af26638efd8f440cbe1851f4e087b106/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 . | 15 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-b4723e5198e6472c8f2d26e0af643c6f | 3 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 114 | artifacts/raw/trivy-config.json |
| 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 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-b4723e5198e6472c8f2d26e0af643c6f | 0 | artifacts/raw/osv-scanner.json |