Executive summary
fatedier/frp is rated At risk because critical security findings are open. Its score is held back in part because it has uses of packages that aren't listed. It scores 54 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 41, is the weakest lens and counts most in the score. The best first step is fixing the two tests that passed on some runs and failed on others, worth about 9 points. Tidying the declared packages would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 62 would lift the score to about 63.
Ten known security holes in the packages the code depends on can be used by attackers. Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four secrets can leak from the build pipeline. Updating the vulnerable packages, pinning each tool to an exact version and limiting each secret to its own step would close these risks. The four unsafe settings in infrastructure or container files need changing to safe values. The two connections that skip the certificate check need the certificate check switched back on. The four uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 30,969 lines, about €58,000 to rebuild.
If Production Readiness rose from 41 to 62, the lowest score rated Strong, the score would rise from 54 to about 63.
New since the last survey: 54 findings
- Code Duplication · Edited copy of a member (84 corresponding lines) client/proxy/sudp.go
- Code Duplication · Edited copy of a member (46 corresponding lines) server/http/controller_v2.go
- Code Duplication · Edited copy of a member (33 corresponding lines) server/group/https.go
- Code Duplication · Edited copy of a member (37 corresponding lines) pkg/config/types/types.go
- Code Duplication · Edited copy of a member (31 corresponding lines) cmd/frpc/sub/proxy.go
- Code Duplication · Edited copy of a member (31 corresponding lines) client/config_manager.go
- Code Duplication · Edited copy of a member (27 corresponding lines) pkg/config/v1/decode.go
- Code Duplication · Edited copy of a member (22 corresponding lines) pkg/util/http/handler.go
- Code Duplication · Edited copy of a member (28 corresponding lines) client/proxy/xtcp.go
- Code Duplication · Edited copy of a member (26 corresponding lines) pkg/config/v1/decode.go
- Code Duplication · Edited copy of a member (19 corresponding lines) client/http/controller.go
- Code Duplication · Edited copy of a member (25 corresponding lines) pkg/plugin/client/https2http.go
- Code Duplication · Edited copy of a member (22 corresponding lines) client/config_manager.go
- Code Duplication · Edited copy of a member (21 corresponding lines) client/config_manager.go
- Code Duplication · Edited copy of a member (26 corresponding lines) pkg/config/v1/validation/proxy.go
- Code Duplication · Edited copy of a member (15 corresponding lines) pkg/sdk/client/client.go
- Code Duplication · Edited copy of a member (23 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (20 corresponding lines) client/config_manager.go
- Code Duplication · Edited copy of a member (20 corresponding lines) server/group/http.go
- Code Duplication · Edited copy of a member (17 corresponding lines) pkg/auth/auth.go
- Code Duplication · Edited copy of a member (9 corresponding lines) cmd/frpc/sub/root.go
- Code Duplication · Edited copy of a member (21 corresponding lines) server/proxy/proxy.go
- Code Duplication · Edited copies of one member (4 members, 17+ corresponding lines) client/http/controller.go
- Code Duplication · Edited copy of a member (11 corresponding lines) cmd/frpc/sub/admin.go
- Code Duplication · Edited copy of a member (18 corresponding lines) pkg/metrics/text/text.go
- Code Duplication · Edited copy of a member (20 corresponding lines) client/config_manager.go
- Code Duplication · Edited copy of a member (16 corresponding lines) client/config_manager.go
- Code Duplication · Edited copy of a member (17 corresponding lines) pkg/config/legacy/proxy.go
- Code Duplication · Edited copy of a member (15 corresponding lines) pkg/config/source/store.go
- Code Duplication · Edited copy of a member (13 corresponding lines) pkg/config/v1/proxy.go
- Code Duplication · Edited copy of a member (12 corresponding lines) pkg/msg/udp_binary.go
- Code Duplication · Edited copy of a member (9 corresponding lines) pkg/policy/featuregate/feature_gate.go
- Code Duplication · Edited copy of a member (12 corresponding lines) server/http/controller_v2.go
- Code Duplication · Edited copy of a member (12 corresponding lines) client/visitor/xtcp.go
- Code Duplication · Edited copy of a member (15 corresponding lines) pkg/plugin/client/http_proxy.go
- Code Duplication · Edited copy of a member (11 corresponding lines) client/http/model/proxy_definition.go
- Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) client/proxy/proxy_manager.go
- Code Duplication · Edited copy of a member (12 corresponding lines) pkg/config/legacy/proxy.go
- Code Duplication · Edited copy of a member (9 corresponding lines) pkg/plugin/client/plugin.go
- Code Duplication · Edited copy of a member (10 corresponding lines) pkg/vnet/controller.go
- Code Duplication · Edited copy of a member (9 corresponding lines) client/api_router.go
- Code Duplication · Edited copy of a member (9 corresponding lines) client/visitor/visitor_manager.go
- Code Duplication · Edited copy of a member (10 corresponding lines) pkg/config/source/store.go
- Code Duplication · Duplicated block (14 lines × 2) client/config_manager.go
- Code Duplication · Duplicated block (5 lines × 2) pkg/plugin/client/https2http.go
- Test Reliability · Flaky test: .::github.com/fatedier/frp/server.TestNewServiceReleasesListenersOnWebServerFailure/invalid_TLS_certificate
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Exception handling · Swallowed exception (empty catch) web/frpc/src/views/ProxyDetail.vue
- Exception handling · Swallowed exception (empty catch) web/frpc/src/views/ProxyDetail.vue
- Visual & motion safety · Low contrast colour pair in CSS (4.0:1) web/frps/src/App.vue
Fixed since the last survey: 31 findings
- Code Duplication · Duplicated block (14 lines × 2) client/config_manager.go
- Code Duplication · Duplicated block (5 lines × 2) pkg/plugin/client/https2http.go
- Test Reliability · Flaky test: .::github.com/fatedier/frp/server.TestNewServiceReleasesListenersOnWebServerFailure/port_conflict
- Dependency Hygiene · Dependency pinned to a stale untagged commit: k8s.io/utils
- Churn × Complexity Hotspots · Hotspot: server/proxy/udp.go server/proxy/udp.go
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: GO-2026-6603 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Test Coverage · No test reaches this file web/frps/src/utils/format.ts
- Test Coverage · No test reaches this file web/frpc/src/components/visitor-form/VisitorFormLayout.vue
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyRemoteSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyAuthSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/visitor-form/VisitorBaseSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyTransportSection.vue
- Test Coverage · No test reaches this file web/frpc/src/utils/format.ts
- Test Coverage · No test reaches this file web/frpc/src/types/constants.ts
- Test Coverage · No test reaches this file web/frps/src/api/client.ts
- Test Coverage · No test reaches this file web/frpc/src/stores/client.ts
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyHttpSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/visitor-form/VisitorTransportSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyLoadBalanceSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyMetadataSection.vue
- Test Coverage · No test reaches this file web/frpc/src/components/proxy-form/ProxyNatSection.vue
- Test Coverage · No test reaches this file web/frpc/src/main.ts
- Test Coverage · No test reaches this file web/frps/src/main.ts
- Test Coverage · No test reaches this file web/frpc/src/composables/useResponsive.ts
- Test Coverage · No test reaches this file web/frps/src/composables/useResponsive.ts
- Test Coverage · No test reaches this file web/frps/src/api/server.ts
- Exception handling · Swallowed exception (empty catch) web/frpc/src/views/ProxyDetail.vue
- Exception handling · Swallowed exception (empty catch) web/frpc/src/views/ProxyDetail.vue
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €58,000 · Estimate
| Cost to rebuild | €19,000 to €96,000, for 320 to 1,016 hours of work, about 0.4 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 54. 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 | Medium: 30,969 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 github.com/fatedier/frp/pkg/config/types | 2 github.com/fatedier/frp/pkg/policy/security | 3 github.com/fatedier/frp/pkg/proto/wire | 4 github.com/fatedier/frp/pkg/transport | 5 github.com/fatedier/frp/pkg/util/xlog | 6 github.com/fatedier/frp/server/metrics | 7 web.frpc.src.types.proxy-store | 8 web.frps.src.api | 9 github.com/fatedier/frp/pkg/config/v1 | 10 github.com/fatedier/frp/pkg/metrics/mem | 11 github.com/fatedier/frp/server/ports | 12 github.com/fatedier/frp/client/http/model | 13 github.com/fatedier/frp/pkg/config/source | 14 github.com/fatedier/frp/pkg/config/v1/validation | 15 github.com/fatedier/frp/pkg/plugin/server | 16 github.com/fatedier/frp/pkg/plugin/visitor | 17 github.com/fatedier/frp/pkg/util/http | 18 github.com/fatedier/frp/pkg/vnet | 19 github.com/fatedier/frp/pkg/msg | 20 github.com/fatedier/frp/pkg/plugin/client | 21 github.com/fatedier/frp/pkg/util/net | 22 github.com/fatedier/frp/pkg/util/vhost | 23 github.com/fatedier/frp/client/event | 24 github.com/fatedier/frp/client/visitor | 25 github.com/fatedier/frp/pkg/auth | 26 github.com/fatedier/frp/pkg/config | 27 github.com/fatedier/frp/pkg/nathole | 28 github.com/fatedier/frp/server/group | 29 github.com/fatedier/frp/server/visitor | 30 github.com/fatedier/frp/client/proxy | 31 github.com/fatedier/frp/server/controller | 32 github.com/fatedier/frp/client/configmgmt | 33 github.com/fatedier/frp/server/proxy | 34 github.com/fatedier/frp/client/http | 35 github.com/fatedier/frp/server/http | 36 github.com/fatedier/frp/client | 37 github.com/fatedier/frp/cmd/frpc/sub | 38 github.com/fatedier/frp/pkg/virtual | 39 github.com/fatedier/frp/pkg/ssh | 40 github.com/fatedier/frp/server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 github.com/fatedier/frp/pkg/config/types | ||||||||||||||||||||||||||||||||||||||||
| 2 github.com/fatedier/frp/pkg/policy/security | ||||||||||||||||||||||||||||||||||||||||
| 3 github.com/fatedier/frp/pkg/proto/wire | ||||||||||||||||||||||||||||||||||||||||
| 4 github.com/fatedier/frp/pkg/transport | ||||||||||||||||||||||||||||||||||||||||
| 5 github.com/fatedier/frp/pkg/util/xlog | ||||||||||||||||||||||||||||||||||||||||
| 6 github.com/fatedier/frp/server/metrics | ||||||||||||||||||||||||||||||||||||||||
| 7 web.frpc.src.types.proxy-store | ||||||||||||||||||||||||||||||||||||||||
| 8 web.frps.src.api | ||||||||||||||||||||||||||||||||||||||||
| 9 github.com/fatedier/frp/pkg/config/v1 | 2 | 10 | ||||||||||||||||||||||||||||||||||||||
| 10 github.com/fatedier/frp/pkg/metrics/mem | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 github.com/fatedier/frp/server/ports | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 github.com/fatedier/frp/client/http/model | 15 | |||||||||||||||||||||||||||||||||||||||
| 13 github.com/fatedier/frp/pkg/config/source | 13 | |||||||||||||||||||||||||||||||||||||||
| 14 github.com/fatedier/frp/pkg/config/v1/validation | 2 | 30 | ||||||||||||||||||||||||||||||||||||||
| 15 github.com/fatedier/frp/pkg/plugin/server | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 16 github.com/fatedier/frp/pkg/plugin/visitor | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 17 github.com/fatedier/frp/pkg/util/http | 3 | |||||||||||||||||||||||||||||||||||||||
| 18 github.com/fatedier/frp/pkg/vnet | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 github.com/fatedier/frp/pkg/msg | 4 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 github.com/fatedier/frp/pkg/plugin/client | 10 | 1 | 4 | |||||||||||||||||||||||||||||||||||||
| 21 github.com/fatedier/frp/pkg/util/net | 1 | 6 | ||||||||||||||||||||||||||||||||||||||
| 22 github.com/fatedier/frp/pkg/util/vhost | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 github.com/fatedier/frp/client/event | 2 | |||||||||||||||||||||||||||||||||||||||
| 24 github.com/fatedier/frp/client/visitor | 3 | 10 | 1 | 3 | 3 | 1 | ||||||||||||||||||||||||||||||||||
| 25 github.com/fatedier/frp/pkg/auth | 11 | 21 | ||||||||||||||||||||||||||||||||||||||
| 26 github.com/fatedier/frp/pkg/config | 2 | 9 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 github.com/fatedier/frp/pkg/nathole | 1 | 9 | ||||||||||||||||||||||||||||||||||||||
| 28 github.com/fatedier/frp/server/group | 2 | 11 | ||||||||||||||||||||||||||||||||||||||
| 29 github.com/fatedier/frp/server/visitor | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 30 github.com/fatedier/frp/client/proxy | 3 | 2 | 9 | 4 | 9 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 31 github.com/fatedier/frp/server/controller | 1 | 1 | 2 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 32 github.com/fatedier/frp/client/configmgmt | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 github.com/fatedier/frp/server/proxy | 2 | 13 | 3 | 8 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 34 github.com/fatedier/frp/client/http | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 35 github.com/fatedier/frp/server/http | 4 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 36 github.com/fatedier/frp/client | 2 | 2 | 1 | 1 | 7 | 5 | 2 | 3 | 10 | 1 | 3 | 5 | 2 | 1 | ||||||||||||||||||||||||||
| 37 github.com/fatedier/frp/cmd/frpc/sub | 1 | 5 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 github.com/fatedier/frp/pkg/virtual | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 39 github.com/fatedier/frp/pkg/ssh | 3 | 3 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 github.com/fatedier/frp/server | 3 | 1 | 1 | 1 | 3 | 3 | 2 | 10 | 1 | 1 | 2 | 2 | 5 | 1 |
9→1 github.com/fatedier/frp/pkg/config/v1 uses github.com/fatedier/frp/pkg/config/types✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/config/v1 uses a type in github.com/fatedier/frp/pkg/config/types.
- The types involved
github.com/fatedier/frp/pkg/config/v1.ProxyTransport→github.com/fatedier/frp/pkg/config/types.BandwidthQuantitygithub.com/fatedier/frp/pkg/config/v1.ServerConfig→github.com/fatedier/frp/pkg/config/types.PortsRange
- Direction
- github.com/fatedier/frp/pkg/config/v1 uses github.com/fatedier/frp/pkg/config/types, so a change to github.com/fatedier/frp/pkg/config/types can break github.com/fatedier/frp/pkg/config/v1, while a change to github.com/fatedier/frp/pkg/config/v1 can't break github.com/fatedier/frp/pkg/config/types.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config/v1 uses a module listed above it, which is the healthy direction.
9→19 github.com/fatedier/frp/pkg/config/v1 uses github.com/fatedier/frp/pkg/msg part of a loop✕
- Connections
- 10 pairs of types, where a type in github.com/fatedier/frp/pkg/config/v1 uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/pkg/config/v1.HTTPProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.HTTPSProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.ProxyBaseConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.ProxyConfigurer→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.STCPProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.SUDPProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.TCPMuxProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.TCPProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.UDPProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/pkg/config/v1.XTCPProxyConfig→github.com/fatedier/frp/pkg/msg.NewProxy
- Direction
- github.com/fatedier/frp/pkg/config/v1 uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/pkg/config/v1, while a change to github.com/fatedier/frp/pkg/config/v1 can't break github.com/fatedier/frp/pkg/msg.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→6 github.com/fatedier/frp/pkg/metrics/mem uses github.com/fatedier/frp/server/metrics✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/metrics/mem uses a type in github.com/fatedier/frp/server/metrics.
- The types involved
github.com/fatedier/frp/pkg/metrics/mem.mem→github.com/fatedier/frp/server/metrics.ServerMetricsgithub.com/fatedier/frp/pkg/metrics/mem.serverMetrics→github.com/fatedier/frp/server/metrics.ServerMetrics
- Direction
- github.com/fatedier/frp/pkg/metrics/mem uses github.com/fatedier/frp/server/metrics, so a change to github.com/fatedier/frp/server/metrics can break github.com/fatedier/frp/pkg/metrics/mem, while a change to github.com/fatedier/frp/pkg/metrics/mem can't break github.com/fatedier/frp/server/metrics.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/metrics/mem uses a module listed above it, which is the healthy direction.
11→1 github.com/fatedier/frp/server/ports uses github.com/fatedier/frp/pkg/config/types✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/ports uses a type in github.com/fatedier/frp/pkg/config/types.
- The types involved
github.com/fatedier/frp/server/ports.ports→github.com/fatedier/frp/pkg/config/types.PortsRange
- Direction
- github.com/fatedier/frp/server/ports uses github.com/fatedier/frp/pkg/config/types, so a change to github.com/fatedier/frp/pkg/config/types can break github.com/fatedier/frp/server/ports, while a change to github.com/fatedier/frp/server/ports can't break github.com/fatedier/frp/pkg/config/types.
- Position
- Below the diagonal: github.com/fatedier/frp/server/ports uses a module listed above it, which is the healthy direction.
12→9 github.com/fatedier/frp/client/http/model uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 15 pairs of types, where a type in github.com/fatedier/frp/client/http/model uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.HTTPProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.HTTPSProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.STCPProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.SUDPProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.TCPMuxProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.TCPProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.UDPProxyConfiggithub.com/fatedier/frp/client/http/model.ProxyDefinition→github.com/fatedier/frp/pkg/config/v1.XTCPProxyConfiggithub.com/fatedier/frp/client/http/model.VisitorDefinition→github.com/fatedier/frp/pkg/config/v1.STCPVisitorConfiggithub.com/fatedier/frp/client/http/model.VisitorDefinition→github.com/fatedier/frp/pkg/config/v1.SUDPVisitorConfiggithub.com/fatedier/frp/client/http/model.VisitorDefinition→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/client/http/model.VisitorDefinition→github.com/fatedier/frp/pkg/config/v1.XTCPVisitorConfiggithub.com/fatedier/frp/client/http/model.model→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client/http/model.model→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurer
- Direction
- github.com/fatedier/frp/client/http/model uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/client/http/model, while a change to github.com/fatedier/frp/client/http/model can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/client/http/model uses a module listed above it, which is the healthy direction.
13→9 github.com/fatedier/frp/pkg/config/source uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 13 pairs of types, where a type in github.com/fatedier/frp/pkg/config/source uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/config/source.Aggregator→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/source.Aggregator→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/pkg/config/source.ConfigSource→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/source.ConfigSource→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/pkg/config/source.Source→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/source.StoreSource→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/source.StoreSource→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/pkg/config/source.baseSource→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/source.baseSource→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/pkg/config/source.source→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/source.source→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/pkg/config/source.storeData→github.com/fatedier/frp/pkg/config/v1.TypedProxyConfiggithub.com/fatedier/frp/pkg/config/source.storeData→github.com/fatedier/frp/pkg/config/v1.TypedVisitorConfig
- Direction
- github.com/fatedier/frp/pkg/config/source uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/config/source, while a change to github.com/fatedier/frp/pkg/config/source can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config/source uses a module listed above it, which is the healthy direction.
14→2 github.com/fatedier/frp/pkg/config/v1/validation uses github.com/fatedier/frp/pkg/policy/security✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/config/v1/validation uses a type in github.com/fatedier/frp/pkg/policy/security.
- The types involved
github.com/fatedier/frp/pkg/config/v1/validation.ConfigValidator→github.com/fatedier/frp/pkg/policy/security.UnsafeFeaturesgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/policy/security.UnsafeFeatures
- Direction
- github.com/fatedier/frp/pkg/config/v1/validation uses github.com/fatedier/frp/pkg/policy/security, so a change to github.com/fatedier/frp/pkg/policy/security can break github.com/fatedier/frp/pkg/config/v1/validation, while a change to github.com/fatedier/frp/pkg/config/v1/validation can't break github.com/fatedier/frp/pkg/policy/security.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config/v1/validation uses a module listed above it, which is the healthy direction.
14→9 github.com/fatedier/frp/pkg/config/v1/validation uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 30 pairs of types, where a type in github.com/fatedier/frp/pkg/config/v1/validation uses a type in github.com/fatedier/frp/pkg/config/v1. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
github.com/fatedier/frp/pkg/config/v1/validation.ConfigValidator→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/pkg/config/v1/validation.ConfigValidator→github.com/fatedier/frp/pkg/config/v1.ValueSourcegithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.AuthMethodgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.AuthOIDCClientConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.AuthScopegithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.ClientPluginOptionsgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.DomainConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.HTTP2HTTPSPluginOptionsgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.HTTPProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.HTTPS2HTTPPluginOptionsgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.HTTPS2HTTPSPluginOptionsgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.HTTPSProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.LogConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.MetricsServerConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.ProxyBaseConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.STCPProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.SUDPProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.StaticFilePluginOptionsgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.TCPMuxProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.TCPProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.TLS2RawPluginOptionsgithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.UDPProxyConfiggithub.com/fatedier/frp/pkg/config/v1/validation.validation→github.com/fatedier/frp/pkg/config/v1.UnixDomainSocketPluginOptions
- Direction
- github.com/fatedier/frp/pkg/config/v1/validation uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/config/v1/validation, while a change to github.com/fatedier/frp/pkg/config/v1/validation can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config/v1/validation uses a module listed above it, which is the healthy direction.
15→5 github.com/fatedier/frp/pkg/plugin/server uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/plugin/server uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/pkg/plugin/server.server→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/pkg/plugin/server uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/pkg/plugin/server, while a change to github.com/fatedier/frp/pkg/plugin/server can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/plugin/server uses a module listed above it, which is the healthy direction.
15→9 github.com/fatedier/frp/pkg/plugin/server uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/plugin/server uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/plugin/server.httpPlugin→github.com/fatedier/frp/pkg/config/v1.HTTPPluginOptionsgithub.com/fatedier/frp/pkg/plugin/server.server→github.com/fatedier/frp/pkg/config/v1.HTTPPluginOptions
- Direction
- github.com/fatedier/frp/pkg/plugin/server uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/plugin/server, while a change to github.com/fatedier/frp/pkg/plugin/server can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/plugin/server uses a module listed above it, which is the healthy direction.
16→5 github.com/fatedier/frp/pkg/plugin/visitor uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/plugin/visitor uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/pkg/plugin/visitor.VirtualNetPlugin→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/pkg/plugin/visitor uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/pkg/plugin/visitor, while a change to github.com/fatedier/frp/pkg/plugin/visitor can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/plugin/visitor uses a module listed above it, which is the healthy direction.
16→9 github.com/fatedier/frp/pkg/plugin/visitor uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/plugin/visitor uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/plugin/visitor.visitor→github.com/fatedier/frp/pkg/config/v1.VisitorPluginOptions
- Direction
- github.com/fatedier/frp/pkg/plugin/visitor uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/plugin/visitor, while a change to github.com/fatedier/frp/pkg/plugin/visitor can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/plugin/visitor uses a module listed above it, which is the healthy direction.
16→18 github.com/fatedier/frp/pkg/plugin/visitor uses github.com/fatedier/frp/pkg/vnet part of a loop✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/plugin/visitor uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/pkg/plugin/visitor.PluginContext→github.com/fatedier/frp/pkg/vnet.Controller
- Direction
- github.com/fatedier/frp/pkg/plugin/visitor uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/pkg/plugin/visitor, while a change to github.com/fatedier/frp/pkg/plugin/visitor can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→9 github.com/fatedier/frp/pkg/util/http uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/pkg/util/http uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/util/http.http→github.com/fatedier/frp/pkg/config/v1.MetricsServerConfiggithub.com/fatedier/frp/pkg/util/http.http→github.com/fatedier/frp/pkg/config/v1.TLSConfiggithub.com/fatedier/frp/pkg/util/http.http→github.com/fatedier/frp/pkg/config/v1.WebServerConfig
- Direction
- github.com/fatedier/frp/pkg/util/http uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/util/http, while a change to github.com/fatedier/frp/pkg/util/http can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/util/http uses a module listed above it, which is the healthy direction.
18→9 github.com/fatedier/frp/pkg/vnet uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/vnet uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/vnet.vnet→github.com/fatedier/frp/pkg/config/v1.VirtualNetConfig
- Direction
- github.com/fatedier/frp/pkg/vnet uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/vnet, while a change to github.com/fatedier/frp/pkg/vnet can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/vnet uses a module listed above it, which is the healthy direction.
18→16 github.com/fatedier/frp/pkg/vnet uses github.com/fatedier/frp/pkg/plugin/visitor✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/vnet uses a type in github.com/fatedier/frp/pkg/plugin/visitor.
- The types involved
github.com/fatedier/frp/pkg/vnet.Controller→github.com/fatedier/frp/pkg/plugin/visitor.clientRouteController
- Direction
- github.com/fatedier/frp/pkg/vnet uses github.com/fatedier/frp/pkg/plugin/visitor, so a change to github.com/fatedier/frp/pkg/plugin/visitor can break github.com/fatedier/frp/pkg/vnet, while a change to github.com/fatedier/frp/pkg/vnet can't break github.com/fatedier/frp/pkg/plugin/visitor.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/vnet uses a module listed above it, which is the healthy direction.
19→3 github.com/fatedier/frp/pkg/msg uses github.com/fatedier/frp/pkg/proto/wire✕
- Connections
- 4 pairs of types, where a type in github.com/fatedier/frp/pkg/msg uses a type in github.com/fatedier/frp/pkg/proto/wire.
- The types involved
github.com/fatedier/frp/pkg/msg.V2BinaryUDPPacketReadWriter→github.com/fatedier/frp/pkg/proto/wire.Conngithub.com/fatedier/frp/pkg/msg.V2ReadWriter→github.com/fatedier/frp/pkg/proto/wire.Conngithub.com/fatedier/frp/pkg/msg.msg→github.com/fatedier/frp/pkg/proto/wire.Conngithub.com/fatedier/frp/pkg/msg.msg→github.com/fatedier/frp/pkg/proto/wire.Frame
- Direction
- github.com/fatedier/frp/pkg/msg uses github.com/fatedier/frp/pkg/proto/wire, so a change to github.com/fatedier/frp/pkg/proto/wire can break github.com/fatedier/frp/pkg/msg, while a change to github.com/fatedier/frp/pkg/msg can't break github.com/fatedier/frp/pkg/proto/wire.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/msg uses a module listed above it, which is the healthy direction.
19→18 github.com/fatedier/frp/pkg/msg uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/msg uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/pkg/msg.Conn→github.com/fatedier/frp/pkg/vnet.TunDevice
- Direction
- github.com/fatedier/frp/pkg/msg uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/pkg/msg, while a change to github.com/fatedier/frp/pkg/msg can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/msg uses a module listed above it, which is the healthy direction.
20→9 github.com/fatedier/frp/pkg/plugin/client uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 10 pairs of types, where a type in github.com/fatedier/frp/pkg/plugin/client uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/plugin/client.HTTP2HTTPPlugin→github.com/fatedier/frp/pkg/config/v1.HTTP2HTTPPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.HTTP2HTTPSPlugin→github.com/fatedier/frp/pkg/config/v1.HTTP2HTTPSPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.HTTPProxy→github.com/fatedier/frp/pkg/config/v1.HTTPProxyPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.HTTPS2HTTPPlugin→github.com/fatedier/frp/pkg/config/v1.HTTPS2HTTPPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.HTTPS2HTTPSPlugin→github.com/fatedier/frp/pkg/config/v1.HTTPS2HTTPSPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.StaticFilePlugin→github.com/fatedier/frp/pkg/config/v1.StaticFilePluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.TLS2RawPlugin→github.com/fatedier/frp/pkg/config/v1.TLS2RawPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.VirtualNetPlugin→github.com/fatedier/frp/pkg/config/v1.VirtualNetPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.client→github.com/fatedier/frp/pkg/config/v1.ClientPluginOptionsgithub.com/fatedier/frp/pkg/plugin/client.client→github.com/fatedier/frp/pkg/config/v1.HeaderOperations
- Direction
- github.com/fatedier/frp/pkg/plugin/client uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/plugin/client, while a change to github.com/fatedier/frp/pkg/plugin/client can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/plugin/client uses a module listed above it, which is the healthy direction.
20→18 github.com/fatedier/frp/pkg/plugin/client uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/plugin/client uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/pkg/plugin/client.PluginContext→github.com/fatedier/frp/pkg/vnet.Controller
- Direction
- github.com/fatedier/frp/pkg/plugin/client uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/pkg/plugin/client, while a change to github.com/fatedier/frp/pkg/plugin/client can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/plugin/client uses a module listed above it, which is the healthy direction.
20→30 github.com/fatedier/frp/pkg/plugin/client uses github.com/fatedier/frp/client/proxy part of a loop✕
- Connections
- 4 pairs of types, where a type in github.com/fatedier/frp/pkg/plugin/client uses a type in github.com/fatedier/frp/client/proxy.
- The types involved
github.com/fatedier/frp/pkg/plugin/client.HTTP2HTTPPlugin→github.com/fatedier/frp/client/proxy.reloadablePlugingithub.com/fatedier/frp/pkg/plugin/client.HTTP2HTTPSPlugin→github.com/fatedier/frp/client/proxy.reloadablePlugingithub.com/fatedier/frp/pkg/plugin/client.HTTPS2HTTPPlugin→github.com/fatedier/frp/client/proxy.reloadablePlugingithub.com/fatedier/frp/pkg/plugin/client.HTTPS2HTTPSPlugin→github.com/fatedier/frp/client/proxy.reloadablePlugin
- Direction
- github.com/fatedier/frp/pkg/plugin/client uses github.com/fatedier/frp/client/proxy, so a change to github.com/fatedier/frp/client/proxy can break github.com/fatedier/frp/pkg/plugin/client, while a change to github.com/fatedier/frp/pkg/plugin/client can't break github.com/fatedier/frp/client/proxy.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→5 github.com/fatedier/frp/pkg/util/net uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/util/net uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/pkg/util/net.net→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/pkg/util/net uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/pkg/util/net, while a change to github.com/fatedier/frp/pkg/util/net can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/util/net uses a module listed above it, which is the healthy direction.
21→18 github.com/fatedier/frp/pkg/util/net uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 6 pairs of types, where a type in github.com/fatedier/frp/pkg/util/net uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/pkg/util/net.CloseNotifyConn→github.com/fatedier/frp/pkg/vnet.TunDevicegithub.com/fatedier/frp/pkg/util/net.ConnectedUDPConn→github.com/fatedier/frp/pkg/vnet.TunDevicegithub.com/fatedier/frp/pkg/util/net.ContextConn→github.com/fatedier/frp/pkg/vnet.TunDevicegithub.com/fatedier/frp/pkg/util/net.FakeUDPConn→github.com/fatedier/frp/pkg/vnet.TunDevicegithub.com/fatedier/frp/pkg/util/net.StatsConn→github.com/fatedier/frp/pkg/vnet.TunDevicegithub.com/fatedier/frp/pkg/util/net.WrapReadWriteCloserConn→github.com/fatedier/frp/pkg/vnet.TunDevice
- Direction
- github.com/fatedier/frp/pkg/util/net uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/pkg/util/net, while a change to github.com/fatedier/frp/pkg/util/net can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/util/net uses a module listed above it, which is the healthy direction.
22→18 github.com/fatedier/frp/pkg/util/vhost uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/util/vhost uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/pkg/util/vhost.readOnlyConn→github.com/fatedier/frp/pkg/vnet.TunDevice
- Direction
- github.com/fatedier/frp/pkg/util/vhost uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/pkg/util/vhost, while a change to github.com/fatedier/frp/pkg/util/vhost can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/util/vhost uses a module listed above it, which is the healthy direction.
23→19 github.com/fatedier/frp/client/event uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client/event uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/client/event.CloseProxyPayload→github.com/fatedier/frp/pkg/msg.CloseProxygithub.com/fatedier/frp/client/event.StartProxyPayload→github.com/fatedier/frp/pkg/msg.NewProxy
- Direction
- github.com/fatedier/frp/client/event uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/client/event, while a change to github.com/fatedier/frp/client/event can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/client/event uses a module listed above it, which is the healthy direction.
24→4 github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/transport✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/client/visitor uses a type in github.com/fatedier/frp/pkg/transport.
- The types involved
github.com/fatedier/frp/client/visitor.Helper→github.com/fatedier/frp/pkg/transport.MessageTransportergithub.com/fatedier/frp/client/visitor.visitor→github.com/fatedier/frp/pkg/transport.MessageTransportergithub.com/fatedier/frp/client/visitor.visitorHelperImpl→github.com/fatedier/frp/pkg/transport.MessageTransporter
- Direction
- github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/transport, so a change to github.com/fatedier/frp/pkg/transport can break github.com/fatedier/frp/client/visitor, while a change to github.com/fatedier/frp/client/visitor can't break github.com/fatedier/frp/pkg/transport.
- Position
- Below the diagonal: github.com/fatedier/frp/client/visitor uses a module listed above it, which is the healthy direction.
24→9 github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 10 pairs of types, where a type in github.com/fatedier/frp/client/visitor uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/client/visitor.BaseVisitor→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/client/visitor.BaseVisitor→github.com/fatedier/frp/pkg/config/v1.VisitorBaseConfiggithub.com/fatedier/frp/client/visitor.Manager→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/client/visitor.QUICTunnelSession→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/client/visitor.STCPVisitor→github.com/fatedier/frp/pkg/config/v1.STCPVisitorConfiggithub.com/fatedier/frp/client/visitor.SUDPVisitor→github.com/fatedier/frp/pkg/config/v1.SUDPVisitorConfiggithub.com/fatedier/frp/client/visitor.XTCPVisitor→github.com/fatedier/frp/pkg/config/v1.XTCPVisitorConfiggithub.com/fatedier/frp/client/visitor.visitor→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/client/visitor.visitor→github.com/fatedier/frp/pkg/config/v1.VisitorBaseConfiggithub.com/fatedier/frp/client/visitor.visitor→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurer
- Direction
- github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/client/visitor, while a change to github.com/fatedier/frp/client/visitor can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/client/visitor uses a module listed above it, which is the healthy direction.
24→16 github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/plugin/visitor✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client/visitor uses a type in github.com/fatedier/frp/pkg/plugin/visitor.
- The types involved
github.com/fatedier/frp/client/visitor.BaseVisitor→github.com/fatedier/frp/pkg/plugin/visitor.Plugin
- Direction
- github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/plugin/visitor, so a change to github.com/fatedier/frp/pkg/plugin/visitor can break github.com/fatedier/frp/client/visitor, while a change to github.com/fatedier/frp/client/visitor can't break github.com/fatedier/frp/pkg/plugin/visitor.
- Position
- Below the diagonal: github.com/fatedier/frp/client/visitor uses a module listed above it, which is the healthy direction.
24→18 github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/client/visitor uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/client/visitor.Helper→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client/visitor.visitor→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client/visitor.visitorHelperImpl→github.com/fatedier/frp/pkg/vnet.Controller
- Direction
- github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/client/visitor, while a change to github.com/fatedier/frp/client/visitor can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/client/visitor uses a module listed above it, which is the healthy direction.
24→19 github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/client/visitor uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/client/visitor.Helper→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/client/visitor.SUDPVisitor→github.com/fatedier/frp/pkg/msg.UDPPacketgithub.com/fatedier/frp/client/visitor.visitorHelperImpl→github.com/fatedier/frp/pkg/msg.Conn
- Direction
- github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/client/visitor, while a change to github.com/fatedier/frp/client/visitor can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/client/visitor uses a module listed above it, which is the healthy direction.
24→21 github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/util/net✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client/visitor uses a type in github.com/fatedier/frp/pkg/util/net.
- The types involved
github.com/fatedier/frp/client/visitor.BaseVisitor→github.com/fatedier/frp/pkg/util/net.InternalListener
- Direction
- github.com/fatedier/frp/client/visitor uses github.com/fatedier/frp/pkg/util/net, so a change to github.com/fatedier/frp/pkg/util/net can break github.com/fatedier/frp/client/visitor, while a change to github.com/fatedier/frp/client/visitor can't break github.com/fatedier/frp/pkg/util/net.
- Position
- Below the diagonal: github.com/fatedier/frp/client/visitor uses a module listed above it, which is the healthy direction.
25→9 github.com/fatedier/frp/pkg/auth uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 11 pairs of types, where a type in github.com/fatedier/frp/pkg/auth uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/auth.OidcAuthConsumer→github.com/fatedier/frp/pkg/config/v1.AuthScopegithub.com/fatedier/frp/pkg/auth.OidcAuthProvider→github.com/fatedier/frp/pkg/config/v1.AuthScopegithub.com/fatedier/frp/pkg/auth.OidcTokenSourceAuthProvider→github.com/fatedier/frp/pkg/config/v1.AuthScopegithub.com/fatedier/frp/pkg/auth.OidcTokenSourceAuthProvider→github.com/fatedier/frp/pkg/config/v1.ValueSourcegithub.com/fatedier/frp/pkg/auth.TokenAuthSetterVerifier→github.com/fatedier/frp/pkg/config/v1.AuthScopegithub.com/fatedier/frp/pkg/auth.auth→github.com/fatedier/frp/pkg/config/v1.AuthClientConfiggithub.com/fatedier/frp/pkg/auth.auth→github.com/fatedier/frp/pkg/config/v1.AuthOIDCClientConfiggithub.com/fatedier/frp/pkg/auth.auth→github.com/fatedier/frp/pkg/config/v1.AuthOIDCServerConfiggithub.com/fatedier/frp/pkg/auth.auth→github.com/fatedier/frp/pkg/config/v1.AuthScopegithub.com/fatedier/frp/pkg/auth.auth→github.com/fatedier/frp/pkg/config/v1.AuthServerConfiggithub.com/fatedier/frp/pkg/auth.auth→github.com/fatedier/frp/pkg/config/v1.ValueSource
- Direction
- github.com/fatedier/frp/pkg/auth uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/auth, while a change to github.com/fatedier/frp/pkg/auth can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/auth uses a module listed above it, which is the healthy direction.
25→19 github.com/fatedier/frp/pkg/auth uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 21 pairs of types, where a type in github.com/fatedier/frp/pkg/auth uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/pkg/auth.OidcAuthConsumer→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.OidcAuthConsumer→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.OidcAuthConsumer→github.com/fatedier/frp/pkg/msg.Pinggithub.com/fatedier/frp/pkg/auth.OidcAuthProvider→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.OidcAuthProvider→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.OidcAuthProvider→github.com/fatedier/frp/pkg/msg.Pinggithub.com/fatedier/frp/pkg/auth.OidcTokenSourceAuthProvider→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.OidcTokenSourceAuthProvider→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.OidcTokenSourceAuthProvider→github.com/fatedier/frp/pkg/msg.Pinggithub.com/fatedier/frp/pkg/auth.Setter→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.Setter→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.Setter→github.com/fatedier/frp/pkg/msg.Pinggithub.com/fatedier/frp/pkg/auth.TokenAuthSetterVerifier→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.TokenAuthSetterVerifier→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.TokenAuthSetterVerifier→github.com/fatedier/frp/pkg/msg.Pinggithub.com/fatedier/frp/pkg/auth.Verifier→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.Verifier→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.Verifier→github.com/fatedier/frp/pkg/msg.Pinggithub.com/fatedier/frp/pkg/auth.alwaysPass→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/pkg/auth.alwaysPass→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/pkg/auth.alwaysPass→github.com/fatedier/frp/pkg/msg.Ping
- Direction
- github.com/fatedier/frp/pkg/auth uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/pkg/auth, while a change to github.com/fatedier/frp/pkg/auth can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/auth uses a module listed above it, which is the healthy direction.
26→1 github.com/fatedier/frp/pkg/config uses github.com/fatedier/frp/pkg/config/types✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/config uses a type in github.com/fatedier/frp/pkg/config/types.
- The types involved
github.com/fatedier/frp/pkg/config.BandwidthQuantityFlag→github.com/fatedier/frp/pkg/config/types.BandwidthQuantitygithub.com/fatedier/frp/pkg/config.PortsRangeSliceFlag→github.com/fatedier/frp/pkg/config/types.PortsRange
- Direction
- github.com/fatedier/frp/pkg/config uses github.com/fatedier/frp/pkg/config/types, so a change to github.com/fatedier/frp/pkg/config/types can break github.com/fatedier/frp/pkg/config, while a change to github.com/fatedier/frp/pkg/config can't break github.com/fatedier/frp/pkg/config/types.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config uses a module listed above it, which is the healthy direction.
26→9 github.com/fatedier/frp/pkg/config uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 9 pairs of types, where a type in github.com/fatedier/frp/pkg/config uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/config.ClientConfigLoadResult→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config.ClientConfigLoadResult→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.DomainConfiggithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.ProxyBaseConfiggithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.VisitorBaseConfiggithub.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurer
- Direction
- github.com/fatedier/frp/pkg/config uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/config, while a change to github.com/fatedier/frp/pkg/config can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config uses a module listed above it, which is the healthy direction.
26→19 github.com/fatedier/frp/pkg/config uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/config uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/pkg/config.config→github.com/fatedier/frp/pkg/msg.NewProxy
- Direction
- github.com/fatedier/frp/pkg/config uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/pkg/config, while a change to github.com/fatedier/frp/pkg/config can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/config uses a module listed above it, which is the healthy direction.
27→4 github.com/fatedier/frp/pkg/nathole uses github.com/fatedier/frp/pkg/transport✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/nathole uses a type in github.com/fatedier/frp/pkg/transport.
- The types involved
github.com/fatedier/frp/pkg/nathole.nathole→github.com/fatedier/frp/pkg/transport.MessageTransporter
- Direction
- github.com/fatedier/frp/pkg/nathole uses github.com/fatedier/frp/pkg/transport, so a change to github.com/fatedier/frp/pkg/transport can break github.com/fatedier/frp/pkg/nathole, while a change to github.com/fatedier/frp/pkg/nathole can't break github.com/fatedier/frp/pkg/transport.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/nathole uses a module listed above it, which is the healthy direction.
27→19 github.com/fatedier/frp/pkg/nathole uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 9 pairs of types, where a type in github.com/fatedier/frp/pkg/nathole uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/pkg/nathole.Controller→github.com/fatedier/frp/pkg/msg.NatHoleClientgithub.com/fatedier/frp/pkg/nathole.Controller→github.com/fatedier/frp/pkg/msg.NatHoleReportgithub.com/fatedier/frp/pkg/nathole.Controller→github.com/fatedier/frp/pkg/msg.NatHoleRespgithub.com/fatedier/frp/pkg/nathole.Controller→github.com/fatedier/frp/pkg/msg.NatHoleVisitorgithub.com/fatedier/frp/pkg/nathole.Session→github.com/fatedier/frp/pkg/msg.NatHoleClientgithub.com/fatedier/frp/pkg/nathole.Session→github.com/fatedier/frp/pkg/msg.NatHoleRespgithub.com/fatedier/frp/pkg/nathole.Session→github.com/fatedier/frp/pkg/msg.NatHoleVisitorgithub.com/fatedier/frp/pkg/nathole.nathole→github.com/fatedier/frp/pkg/msg.NatHoleRespgithub.com/fatedier/frp/pkg/nathole.nathole→github.com/fatedier/frp/pkg/msg.PortsRange
- Direction
- github.com/fatedier/frp/pkg/nathole uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/pkg/nathole, while a change to github.com/fatedier/frp/pkg/nathole can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/nathole uses a module listed above it, which is the healthy direction.
28→11 github.com/fatedier/frp/server/group uses github.com/fatedier/frp/server/ports✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server/group uses a type in github.com/fatedier/frp/server/ports.
- The types involved
github.com/fatedier/frp/server/group.TCPGroupCtl→github.com/fatedier/frp/server/ports.Managergithub.com/fatedier/frp/server/group.group→github.com/fatedier/frp/server/ports.Manager
- Direction
- github.com/fatedier/frp/server/group uses github.com/fatedier/frp/server/ports, so a change to github.com/fatedier/frp/server/ports can break github.com/fatedier/frp/server/group, while a change to github.com/fatedier/frp/server/group can't break github.com/fatedier/frp/server/ports.
- Position
- Below the diagonal: github.com/fatedier/frp/server/group uses a module listed above it, which is the healthy direction.
28→22 github.com/fatedier/frp/server/group uses github.com/fatedier/frp/pkg/util/vhost✕
- Connections
- 11 pairs of types, where a type in github.com/fatedier/frp/server/group uses a type in github.com/fatedier/frp/pkg/util/vhost.
- The types involved
github.com/fatedier/frp/server/group.HTTPGroup→github.com/fatedier/frp/pkg/util/vhost.CreateConnFuncgithub.com/fatedier/frp/server/group.HTTPGroup→github.com/fatedier/frp/pkg/util/vhost.RouteConfiggithub.com/fatedier/frp/server/group.HTTPGroupController→github.com/fatedier/frp/pkg/util/vhost.RouteConfiggithub.com/fatedier/frp/server/group.HTTPGroupController→github.com/fatedier/frp/pkg/util/vhost.Routersgithub.com/fatedier/frp/server/group.HTTPSGroup→github.com/fatedier/frp/pkg/util/vhost.RouteConfiggithub.com/fatedier/frp/server/group.HTTPSGroupController→github.com/fatedier/frp/pkg/util/vhost.HTTPSMuxergithub.com/fatedier/frp/server/group.HTTPSGroupController→github.com/fatedier/frp/pkg/util/vhost.RouteConfiggithub.com/fatedier/frp/server/group.TCPMuxGroup→github.com/fatedier/frp/pkg/util/vhost.RouteConfiggithub.com/fatedier/frp/server/group.TCPMuxGroupCtl→github.com/fatedier/frp/pkg/util/vhost.RouteConfiggithub.com/fatedier/frp/server/group.group→github.com/fatedier/frp/pkg/util/vhost.HTTPSMuxergithub.com/fatedier/frp/server/group.group→github.com/fatedier/frp/pkg/util/vhost.Routers
- Direction
- github.com/fatedier/frp/server/group uses github.com/fatedier/frp/pkg/util/vhost, so a change to github.com/fatedier/frp/pkg/util/vhost can break github.com/fatedier/frp/server/group, while a change to github.com/fatedier/frp/server/group can't break github.com/fatedier/frp/pkg/util/vhost.
- Position
- Below the diagonal: github.com/fatedier/frp/server/group uses a module listed above it, which is the healthy direction.
29→18 github.com/fatedier/frp/server/visitor uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/visitor uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/server/visitor.wireProtocolConn→github.com/fatedier/frp/pkg/vnet.TunDevice
- Direction
- github.com/fatedier/frp/server/visitor uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/server/visitor, while a change to github.com/fatedier/frp/server/visitor can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/server/visitor uses a module listed above it, which is the healthy direction.
29→21 github.com/fatedier/frp/server/visitor uses github.com/fatedier/frp/pkg/util/net✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server/visitor uses a type in github.com/fatedier/frp/pkg/util/net.
- The types involved
github.com/fatedier/frp/server/visitor.Manager→github.com/fatedier/frp/pkg/util/net.InternalListenergithub.com/fatedier/frp/server/visitor.listenerBundle→github.com/fatedier/frp/pkg/util/net.InternalListener
- Direction
- github.com/fatedier/frp/server/visitor uses github.com/fatedier/frp/pkg/util/net, so a change to github.com/fatedier/frp/pkg/util/net can break github.com/fatedier/frp/server/visitor, while a change to github.com/fatedier/frp/server/visitor can't break github.com/fatedier/frp/pkg/util/net.
- Position
- Below the diagonal: github.com/fatedier/frp/server/visitor uses a module listed above it, which is the healthy direction.
30→4 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/transport✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/pkg/transport.
- The types involved
github.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/transport.MessageTransportergithub.com/fatedier/frp/client/proxy.Manager→github.com/fatedier/frp/pkg/transport.MessageTransportergithub.com/fatedier/frp/client/proxy.proxy→github.com/fatedier/frp/pkg/transport.MessageTransporter
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/transport, so a change to github.com/fatedier/frp/pkg/transport can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/pkg/transport.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
30→5 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/util/xlog.Loggergithub.com/fatedier/frp/client/proxy.Wrapper→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
30→9 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 9 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/config/v1.ProxyBaseConfiggithub.com/fatedier/frp/client/proxy.Manager→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client/proxy.SUDPProxy→github.com/fatedier/frp/pkg/config/v1.SUDPProxyConfiggithub.com/fatedier/frp/client/proxy.UDPProxy→github.com/fatedier/frp/pkg/config/v1.UDPProxyConfiggithub.com/fatedier/frp/client/proxy.WorkingStatus→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client/proxy.XTCPProxy→github.com/fatedier/frp/pkg/config/v1.XTCPProxyConfiggithub.com/fatedier/frp/client/proxy.proxy→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/client/proxy.proxy→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurer
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
30→18 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 4 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client/proxy.Manager→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client/proxy.Wrapper→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client/proxy.proxy→github.com/fatedier/frp/pkg/vnet.Controller
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
30→19 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 9 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.Manager→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.Proxy→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.SUDPProxy→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.UDPProxy→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.UDPProxy→github.com/fatedier/frp/pkg/msg.UDPPacketgithub.com/fatedier/frp/client/proxy.Wrapper→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.XTCPProxy→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/client/proxy.proxy→github.com/fatedier/frp/pkg/msg.NatHoleSid
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
30→20 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/plugin/client✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/pkg/plugin/client.
- The types involved
github.com/fatedier/frp/client/proxy.BaseProxy→github.com/fatedier/frp/pkg/plugin/client.Plugingithub.com/fatedier/frp/client/proxy.reloadablePlugin→github.com/fatedier/frp/pkg/plugin/client.Plugin
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/pkg/plugin/client, so a change to github.com/fatedier/frp/pkg/plugin/client can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/pkg/plugin/client.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
30→23 github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/client/event✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client/proxy uses a type in github.com/fatedier/frp/client/event.
- The types involved
github.com/fatedier/frp/client/proxy.Wrapper→github.com/fatedier/frp/client/event.Handlergithub.com/fatedier/frp/client/proxy.proxy→github.com/fatedier/frp/client/event.Handler
- Direction
- github.com/fatedier/frp/client/proxy uses github.com/fatedier/frp/client/event, so a change to github.com/fatedier/frp/client/event can break github.com/fatedier/frp/client/proxy, while a change to github.com/fatedier/frp/client/proxy can't break github.com/fatedier/frp/client/event.
- Position
- Below the diagonal: github.com/fatedier/frp/client/proxy uses a module listed above it, which is the healthy direction.
31→11 github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/server/ports✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/controller uses a type in github.com/fatedier/frp/server/ports.
- The types involved
github.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/server/ports.Manager
- Direction
- github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/server/ports, so a change to github.com/fatedier/frp/server/ports can break github.com/fatedier/frp/server/controller, while a change to github.com/fatedier/frp/server/controller can't break github.com/fatedier/frp/server/ports.
- Position
- Below the diagonal: github.com/fatedier/frp/server/controller uses a module listed above it, which is the healthy direction.
31→15 github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/pkg/plugin/server✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/controller uses a type in github.com/fatedier/frp/pkg/plugin/server.
- The types involved
github.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/pkg/plugin/server.Manager
- Direction
- github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/pkg/plugin/server, so a change to github.com/fatedier/frp/pkg/plugin/server can break github.com/fatedier/frp/server/controller, while a change to github.com/fatedier/frp/server/controller can't break github.com/fatedier/frp/pkg/plugin/server.
- Position
- Below the diagonal: github.com/fatedier/frp/server/controller uses a module listed above it, which is the healthy direction.
31→22 github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/pkg/util/vhost✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server/controller uses a type in github.com/fatedier/frp/pkg/util/vhost.
- The types involved
github.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/pkg/util/vhost.HTTPReverseProxygithub.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/pkg/util/vhost.HTTPSMuxer
- Direction
- github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/pkg/util/vhost, so a change to github.com/fatedier/frp/pkg/util/vhost can break github.com/fatedier/frp/server/controller, while a change to github.com/fatedier/frp/server/controller can't break github.com/fatedier/frp/pkg/util/vhost.
- Position
- Below the diagonal: github.com/fatedier/frp/server/controller uses a module listed above it, which is the healthy direction.
31→27 github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/pkg/nathole✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/controller uses a type in github.com/fatedier/frp/pkg/nathole.
- The types involved
github.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/pkg/nathole.Controller
- Direction
- github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/pkg/nathole, so a change to github.com/fatedier/frp/pkg/nathole can break github.com/fatedier/frp/server/controller, while a change to github.com/fatedier/frp/server/controller can't break github.com/fatedier/frp/pkg/nathole.
- Position
- Below the diagonal: github.com/fatedier/frp/server/controller uses a module listed above it, which is the healthy direction.
31→28 github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/server/group✕
- Connections
- 4 pairs of types, where a type in github.com/fatedier/frp/server/controller uses a type in github.com/fatedier/frp/server/group.
- The types involved
github.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/server/group.HTTPGroupControllergithub.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/server/group.HTTPSGroupControllergithub.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/server/group.TCPGroupCtlgithub.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/server/group.TCPMuxGroupCtl
- Direction
- github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/server/group, so a change to github.com/fatedier/frp/server/group can break github.com/fatedier/frp/server/controller, while a change to github.com/fatedier/frp/server/controller can't break github.com/fatedier/frp/server/group.
- Position
- Below the diagonal: github.com/fatedier/frp/server/controller uses a module listed above it, which is the healthy direction.
31→29 github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/server/visitor✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/controller uses a type in github.com/fatedier/frp/server/visitor.
- The types involved
github.com/fatedier/frp/server/controller.ResourceController→github.com/fatedier/frp/server/visitor.Manager
- Direction
- github.com/fatedier/frp/server/controller uses github.com/fatedier/frp/server/visitor, so a change to github.com/fatedier/frp/server/visitor can break github.com/fatedier/frp/server/controller, while a change to github.com/fatedier/frp/server/controller can't break github.com/fatedier/frp/server/visitor.
- Position
- Below the diagonal: github.com/fatedier/frp/server/controller uses a module listed above it, which is the healthy direction.
32→9 github.com/fatedier/frp/client/configmgmt uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client/configmgmt uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/client/configmgmt.ConfigManager→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client/configmgmt.ConfigManager→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurer
- Direction
- github.com/fatedier/frp/client/configmgmt uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/client/configmgmt, while a change to github.com/fatedier/frp/client/configmgmt can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/client/configmgmt uses a module listed above it, which is the healthy direction.
32→30 github.com/fatedier/frp/client/configmgmt uses github.com/fatedier/frp/client/proxy✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client/configmgmt uses a type in github.com/fatedier/frp/client/proxy.
- The types involved
github.com/fatedier/frp/client/configmgmt.ConfigManager→github.com/fatedier/frp/client/proxy.WorkingStatus
- Direction
- github.com/fatedier/frp/client/configmgmt uses github.com/fatedier/frp/client/proxy, so a change to github.com/fatedier/frp/client/proxy can break github.com/fatedier/frp/client/configmgmt, while a change to github.com/fatedier/frp/client/configmgmt can't break github.com/fatedier/frp/client/proxy.
- Position
- Below the diagonal: github.com/fatedier/frp/client/configmgmt uses a module listed above it, which is the healthy direction.
33→5 github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server/proxy uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/server/proxy.BaseProxy→github.com/fatedier/frp/pkg/util/xlog.Loggergithub.com/fatedier/frp/server/proxy.proxy→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/server/proxy, while a change to github.com/fatedier/frp/server/proxy can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/server/proxy uses a module listed above it, which is the healthy direction.
33→9 github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 13 pairs of types, where a type in github.com/fatedier/frp/server/proxy uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/server/proxy.BaseProxy→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/server/proxy.BaseProxy→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/server/proxy.HTTPProxy→github.com/fatedier/frp/pkg/config/v1.HTTPProxyConfiggithub.com/fatedier/frp/server/proxy.HTTPSProxy→github.com/fatedier/frp/pkg/config/v1.HTTPSProxyConfiggithub.com/fatedier/frp/server/proxy.Options→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/server/proxy.Options→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/server/proxy.Proxy→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/server/proxy.STCPProxy→github.com/fatedier/frp/pkg/config/v1.STCPProxyConfiggithub.com/fatedier/frp/server/proxy.SUDPProxy→github.com/fatedier/frp/pkg/config/v1.SUDPProxyConfiggithub.com/fatedier/frp/server/proxy.TCPMuxProxy→github.com/fatedier/frp/pkg/config/v1.TCPMuxProxyConfiggithub.com/fatedier/frp/server/proxy.TCPProxy→github.com/fatedier/frp/pkg/config/v1.TCPProxyConfiggithub.com/fatedier/frp/server/proxy.UDPProxy→github.com/fatedier/frp/pkg/config/v1.UDPProxyConfiggithub.com/fatedier/frp/server/proxy.XTCPProxy→github.com/fatedier/frp/pkg/config/v1.XTCPProxyConfig
- Direction
- github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/server/proxy, while a change to github.com/fatedier/frp/server/proxy can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/server/proxy uses a module listed above it, which is the healthy direction.
33→15 github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/plugin/server✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/server/proxy uses a type in github.com/fatedier/frp/pkg/plugin/server.
- The types involved
github.com/fatedier/frp/server/proxy.BaseProxy→github.com/fatedier/frp/pkg/plugin/server.UserInfogithub.com/fatedier/frp/server/proxy.Options→github.com/fatedier/frp/pkg/plugin/server.UserInfogithub.com/fatedier/frp/server/proxy.Proxy→github.com/fatedier/frp/pkg/plugin/server.UserInfo
- Direction
- github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/plugin/server, so a change to github.com/fatedier/frp/pkg/plugin/server can break github.com/fatedier/frp/server/proxy, while a change to github.com/fatedier/frp/server/proxy can't break github.com/fatedier/frp/pkg/plugin/server.
- Position
- Below the diagonal: github.com/fatedier/frp/server/proxy uses a module listed above it, which is the healthy direction.
33→19 github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 8 pairs of types, where a type in github.com/fatedier/frp/server/proxy uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/server/proxy.BaseProxy→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/server/proxy.Options→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/server/proxy.Proxy→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/server/proxy.UDPProxy→github.com/fatedier/frp/pkg/msg.UDPPacketgithub.com/fatedier/frp/server/proxy.WorkConn→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/server/proxy.WorkConn→github.com/fatedier/frp/pkg/msg.StartWorkConngithub.com/fatedier/frp/server/proxy.proxy→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/server/proxy.proxy→github.com/fatedier/frp/pkg/msg.ReadWriter
- Direction
- github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/server/proxy, while a change to github.com/fatedier/frp/server/proxy can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/server/proxy uses a module listed above it, which is the healthy direction.
33→22 github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/util/vhost✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/proxy uses a type in github.com/fatedier/frp/pkg/util/vhost.
- The types involved
github.com/fatedier/frp/server/proxy.HTTPSProxy→github.com/fatedier/frp/pkg/util/vhost.RouteConfig
- Direction
- github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/pkg/util/vhost, so a change to github.com/fatedier/frp/pkg/util/vhost can break github.com/fatedier/frp/server/proxy, while a change to github.com/fatedier/frp/server/proxy can't break github.com/fatedier/frp/pkg/util/vhost.
- Position
- Below the diagonal: github.com/fatedier/frp/server/proxy uses a module listed above it, which is the healthy direction.
33→31 github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/server/controller✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/server/proxy uses a type in github.com/fatedier/frp/server/controller.
- The types involved
github.com/fatedier/frp/server/proxy.BaseProxy→github.com/fatedier/frp/server/controller.ResourceControllergithub.com/fatedier/frp/server/proxy.Options→github.com/fatedier/frp/server/controller.ResourceControllergithub.com/fatedier/frp/server/proxy.Proxy→github.com/fatedier/frp/server/controller.ResourceController
- Direction
- github.com/fatedier/frp/server/proxy uses github.com/fatedier/frp/server/controller, so a change to github.com/fatedier/frp/server/controller can break github.com/fatedier/frp/server/proxy, while a change to github.com/fatedier/frp/server/proxy can't break github.com/fatedier/frp/server/controller.
- Position
- Below the diagonal: github.com/fatedier/frp/server/proxy uses a module listed above it, which is the healthy direction.
34→12 github.com/fatedier/frp/client/http uses github.com/fatedier/frp/client/http/model✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client/http uses a type in github.com/fatedier/frp/client/http/model.
- The types involved
github.com/fatedier/frp/client/http.Controller→github.com/fatedier/frp/client/http/model.ProxyStatusResp
- Direction
- github.com/fatedier/frp/client/http uses github.com/fatedier/frp/client/http/model, so a change to github.com/fatedier/frp/client/http/model can break github.com/fatedier/frp/client/http, while a change to github.com/fatedier/frp/client/http can't break github.com/fatedier/frp/client/http/model.
- Position
- Below the diagonal: github.com/fatedier/frp/client/http uses a module listed above it, which is the healthy direction.
34→17 github.com/fatedier/frp/client/http uses github.com/fatedier/frp/pkg/util/http✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client/http uses a type in github.com/fatedier/frp/pkg/util/http.
- The types involved
github.com/fatedier/frp/client/http.Controller→github.com/fatedier/frp/pkg/util/http.Context
- Direction
- github.com/fatedier/frp/client/http uses github.com/fatedier/frp/pkg/util/http, so a change to github.com/fatedier/frp/pkg/util/http can break github.com/fatedier/frp/client/http, while a change to github.com/fatedier/frp/client/http can't break github.com/fatedier/frp/pkg/util/http.
- Position
- Below the diagonal: github.com/fatedier/frp/client/http uses a module listed above it, which is the healthy direction.
34→30 github.com/fatedier/frp/client/http uses github.com/fatedier/frp/client/proxy✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client/http uses a type in github.com/fatedier/frp/client/proxy.
- The types involved
github.com/fatedier/frp/client/http.Controller→github.com/fatedier/frp/client/proxy.WorkingStatus
- Direction
- github.com/fatedier/frp/client/http uses github.com/fatedier/frp/client/proxy, so a change to github.com/fatedier/frp/client/proxy can break github.com/fatedier/frp/client/http, while a change to github.com/fatedier/frp/client/http can't break github.com/fatedier/frp/client/proxy.
- Position
- Below the diagonal: github.com/fatedier/frp/client/http uses a module listed above it, which is the healthy direction.
34→32 github.com/fatedier/frp/client/http uses github.com/fatedier/frp/client/configmgmt✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client/http uses a type in github.com/fatedier/frp/client/configmgmt.
- The types involved
github.com/fatedier/frp/client/http.Controller→github.com/fatedier/frp/client/configmgmt.ConfigManagergithub.com/fatedier/frp/client/http.ControllerParams→github.com/fatedier/frp/client/configmgmt.ConfigManager
- Direction
- github.com/fatedier/frp/client/http uses github.com/fatedier/frp/client/configmgmt, so a change to github.com/fatedier/frp/client/configmgmt can break github.com/fatedier/frp/client/http, while a change to github.com/fatedier/frp/client/http can't break github.com/fatedier/frp/client/configmgmt.
- Position
- Below the diagonal: github.com/fatedier/frp/client/http uses a module listed above it, which is the healthy direction.
35→9 github.com/fatedier/frp/server/http uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 4 pairs of types, where a type in github.com/fatedier/frp/server/http uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/server/http.Controller→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/server/http.http→github.com/fatedier/frp/pkg/config/v1.ProxyBaseConfiggithub.com/fatedier/frp/server/http.http→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/server/http.http→github.com/fatedier/frp/pkg/config/v1.ServerConfig
- Direction
- github.com/fatedier/frp/server/http uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/server/http, while a change to github.com/fatedier/frp/server/http can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/server/http uses a module listed above it, which is the healthy direction.
35→10 github.com/fatedier/frp/server/http uses github.com/fatedier/frp/pkg/metrics/mem✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server/http uses a type in github.com/fatedier/frp/pkg/metrics/mem.
- The types involved
github.com/fatedier/frp/server/http.Controller→github.com/fatedier/frp/pkg/metrics/mem.ProxyStatsgithub.com/fatedier/frp/server/http.http→github.com/fatedier/frp/pkg/metrics/mem.ProxyTrafficInfo
- Direction
- github.com/fatedier/frp/server/http uses github.com/fatedier/frp/pkg/metrics/mem, so a change to github.com/fatedier/frp/pkg/metrics/mem can break github.com/fatedier/frp/server/http, while a change to github.com/fatedier/frp/server/http can't break github.com/fatedier/frp/pkg/metrics/mem.
- Position
- Below the diagonal: github.com/fatedier/frp/server/http uses a module listed above it, which is the healthy direction.
35→17 github.com/fatedier/frp/server/http uses github.com/fatedier/frp/pkg/util/http✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server/http uses a type in github.com/fatedier/frp/pkg/util/http.
- The types involved
github.com/fatedier/frp/server/http.Controller→github.com/fatedier/frp/pkg/util/http.Contextgithub.com/fatedier/frp/server/http.http→github.com/fatedier/frp/pkg/util/http.Context
- Direction
- github.com/fatedier/frp/server/http uses github.com/fatedier/frp/pkg/util/http, so a change to github.com/fatedier/frp/pkg/util/http can break github.com/fatedier/frp/server/http, while a change to github.com/fatedier/frp/server/http can't break github.com/fatedier/frp/pkg/util/http.
- Position
- Below the diagonal: github.com/fatedier/frp/server/http uses a module listed above it, which is the healthy direction.
35→33 github.com/fatedier/frp/server/http uses github.com/fatedier/frp/server/proxy✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server/http uses a type in github.com/fatedier/frp/server/proxy.
- The types involved
github.com/fatedier/frp/server/http.ProxyManager→github.com/fatedier/frp/server/proxy.Proxy
- Direction
- github.com/fatedier/frp/server/http uses github.com/fatedier/frp/server/proxy, so a change to github.com/fatedier/frp/server/proxy can break github.com/fatedier/frp/server/http, while a change to github.com/fatedier/frp/server/http can't break github.com/fatedier/frp/server/proxy.
- Position
- Below the diagonal: github.com/fatedier/frp/server/http uses a module listed above it, which is the healthy direction.
36→2 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/policy/security✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/policy/security.
- The types involved
github.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/policy/security.UnsafeFeaturesgithub.com/fatedier/frp/client.ServiceOptions→github.com/fatedier/frp/pkg/policy/security.UnsafeFeatures
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/policy/security, so a change to github.com/fatedier/frp/pkg/policy/security can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/policy/security.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→3 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/proto/wire✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/proto/wire.
- The types involved
github.com/fatedier/frp/client.controlSessionDialer→github.com/fatedier/frp/pkg/proto/wire.CryptoContextgithub.com/fatedier/frp/client.loginExchangeResult→github.com/fatedier/frp/pkg/proto/wire.CryptoContext
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/proto/wire, so a change to github.com/fatedier/frp/pkg/proto/wire can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/proto/wire.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→4 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/transport✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/transport.
- The types involved
github.com/fatedier/frp/client.Control→github.com/fatedier/frp/pkg/transport.MessageTransporter
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/transport, so a change to github.com/fatedier/frp/pkg/transport can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/transport.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→5 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/client.Control→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→9 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 7 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/client.Control→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client.Control→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/client.SessionContext→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/client.serviceConfigManager→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/client.serviceConfigManager→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurer
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→13 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/config/source✕
- Connections
- 5 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/config/source.
- The types involved
github.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/config/source.Aggregatorgithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/config/source.ConfigSourcegithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/config/source.StoreSourcegithub.com/fatedier/frp/client.ServiceOptions→github.com/fatedier/frp/pkg/config/source.Aggregatorgithub.com/fatedier/frp/client.serviceConfigManager→github.com/fatedier/frp/pkg/config/source.StoreSource
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/config/source, so a change to github.com/fatedier/frp/pkg/config/source can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/config/source.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→17 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/util/http✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/util/http.
- The types involved
github.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/util/http.RouterRegisterHelpergithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/util/http.Server
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/util/http, so a change to github.com/fatedier/frp/pkg/util/http can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/util/http.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→18 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/vnet✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/vnet.
- The types involved
github.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client.SessionContext→github.com/fatedier/frp/pkg/vnet.Controllergithub.com/fatedier/frp/client.controlSessionDialer→github.com/fatedier/frp/pkg/vnet.Controller
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/vnet, so a change to github.com/fatedier/frp/pkg/vnet can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/vnet.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→19 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 10 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/client.Control→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/client.Control→github.com/fatedier/frp/pkg/msg.Dispatchergithub.com/fatedier/frp/client.MessageConnector→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/msg.ClientSpecgithub.com/fatedier/frp/client.ServiceOptions→github.com/fatedier/frp/pkg/msg.ClientSpecgithub.com/fatedier/frp/client.SessionContext→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/client.controlSessionDialer→github.com/fatedier/frp/pkg/msg.ClientSpecgithub.com/fatedier/frp/client.controlSessionDialer→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/client.loginExchangeResult→github.com/fatedier/frp/pkg/msg.LoginRespgithub.com/fatedier/frp/client.messageConnector→github.com/fatedier/frp/pkg/msg.Conn
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→24 github.com/fatedier/frp/client uses github.com/fatedier/frp/client/visitor✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/client/visitor.
- The types involved
github.com/fatedier/frp/client.Control→github.com/fatedier/frp/client/visitor.Manager
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/client/visitor, so a change to github.com/fatedier/frp/client/visitor can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/client/visitor.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→25 github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/auth✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/pkg/auth.
- The types involved
github.com/fatedier/frp/client.Service→github.com/fatedier/frp/pkg/auth.ClientAuthgithub.com/fatedier/frp/client.SessionContext→github.com/fatedier/frp/pkg/auth.ClientAuthgithub.com/fatedier/frp/client.controlSessionDialer→github.com/fatedier/frp/pkg/auth.ClientAuth
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/pkg/auth, so a change to github.com/fatedier/frp/pkg/auth can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/pkg/auth.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→30 github.com/fatedier/frp/client uses github.com/fatedier/frp/client/proxy✕
- Connections
- 5 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/client/proxy.
- The types involved
github.com/fatedier/frp/client.Control→github.com/fatedier/frp/client/proxy.Managergithub.com/fatedier/frp/client.Service→github.com/fatedier/frp/client/proxy.WorkingStatusgithub.com/fatedier/frp/client.StatusExporter→github.com/fatedier/frp/client/proxy.WorkingStatusgithub.com/fatedier/frp/client.serviceConfigManager→github.com/fatedier/frp/client/proxy.WorkingStatusgithub.com/fatedier/frp/client.statusExporterImpl→github.com/fatedier/frp/client/proxy.WorkingStatus
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/client/proxy, so a change to github.com/fatedier/frp/client/proxy can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/client/proxy.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→32 github.com/fatedier/frp/client uses github.com/fatedier/frp/client/configmgmt✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/client/configmgmt.
- The types involved
github.com/fatedier/frp/client.client→github.com/fatedier/frp/client/configmgmt.ConfigManagergithub.com/fatedier/frp/client.serviceConfigManager→github.com/fatedier/frp/client/configmgmt.ConfigManager
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/client/configmgmt, so a change to github.com/fatedier/frp/client/configmgmt can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/client/configmgmt.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
36→34 github.com/fatedier/frp/client uses github.com/fatedier/frp/client/http✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/client uses a type in github.com/fatedier/frp/client/http.
- The types involved
github.com/fatedier/frp/client.client→github.com/fatedier/frp/client/http.Controller
- Direction
- github.com/fatedier/frp/client uses github.com/fatedier/frp/client/http, so a change to github.com/fatedier/frp/client/http can break github.com/fatedier/frp/client, while a change to github.com/fatedier/frp/client can't break github.com/fatedier/frp/client/http.
- Position
- Below the diagonal: github.com/fatedier/frp/client uses a module listed above it, which is the healthy direction.
37→2 github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/policy/security✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/cmd/frpc/sub uses a type in github.com/fatedier/frp/pkg/policy/security.
- The types involved
github.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/policy/security.UnsafeFeatures
- Direction
- github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/policy/security, so a change to github.com/fatedier/frp/pkg/policy/security can break github.com/fatedier/frp/cmd/frpc/sub, while a change to github.com/fatedier/frp/cmd/frpc/sub can't break github.com/fatedier/frp/pkg/policy/security.
- Position
- Below the diagonal: github.com/fatedier/frp/cmd/frpc/sub uses a module listed above it, which is the healthy direction.
37→9 github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 5 pairs of types, where a type in github.com/fatedier/frp/cmd/frpc/sub uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/v1.ProxyTypegithub.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/v1.VisitorConfigurergithub.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/v1.VisitorType
- Direction
- github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/cmd/frpc/sub, while a change to github.com/fatedier/frp/cmd/frpc/sub can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/cmd/frpc/sub uses a module listed above it, which is the healthy direction.
37→13 github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config/source✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/cmd/frpc/sub uses a type in github.com/fatedier/frp/pkg/config/source.
- The types involved
github.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/source.Aggregator
- Direction
- github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config/source, so a change to github.com/fatedier/frp/pkg/config/source can break github.com/fatedier/frp/cmd/frpc/sub, while a change to github.com/fatedier/frp/cmd/frpc/sub can't break github.com/fatedier/frp/pkg/config/source.
- Position
- Below the diagonal: github.com/fatedier/frp/cmd/frpc/sub uses a module listed above it, which is the healthy direction.
37→14 github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config/v1/validation✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/cmd/frpc/sub uses a type in github.com/fatedier/frp/pkg/config/v1/validation.
- The types involved
github.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config/v1/validation.Warning
- Direction
- github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config/v1/validation, so a change to github.com/fatedier/frp/pkg/config/v1/validation can break github.com/fatedier/frp/cmd/frpc/sub, while a change to github.com/fatedier/frp/cmd/frpc/sub can't break github.com/fatedier/frp/pkg/config/v1/validation.
- Position
- Below the diagonal: github.com/fatedier/frp/cmd/frpc/sub uses a module listed above it, which is the healthy direction.
37→26 github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/cmd/frpc/sub uses a type in github.com/fatedier/frp/pkg/config.
- The types involved
github.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/pkg/config.ClientConfigLoadResult
- Direction
- github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/pkg/config, so a change to github.com/fatedier/frp/pkg/config can break github.com/fatedier/frp/cmd/frpc/sub, while a change to github.com/fatedier/frp/cmd/frpc/sub can't break github.com/fatedier/frp/pkg/config.
- Position
- Below the diagonal: github.com/fatedier/frp/cmd/frpc/sub uses a module listed above it, which is the healthy direction.
37→36 github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/client✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/cmd/frpc/sub uses a type in github.com/fatedier/frp/client.
- The types involved
github.com/fatedier/frp/cmd/frpc/sub.sub→github.com/fatedier/frp/client.Service
- Direction
- github.com/fatedier/frp/cmd/frpc/sub uses github.com/fatedier/frp/client, so a change to github.com/fatedier/frp/client can break github.com/fatedier/frp/cmd/frpc/sub, while a change to github.com/fatedier/frp/cmd/frpc/sub can't break github.com/fatedier/frp/client.
- Position
- Below the diagonal: github.com/fatedier/frp/cmd/frpc/sub uses a module listed above it, which is the healthy direction.
38→9 github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/virtual uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/virtual.Client→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/virtual.ClientOptions→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfig
- Direction
- github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/virtual, while a change to github.com/fatedier/frp/pkg/virtual can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/virtual uses a module listed above it, which is the healthy direction.
38→19 github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/virtual uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/pkg/virtual.ClientOptions→github.com/fatedier/frp/pkg/msg.ClientSpec
- Direction
- github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/pkg/virtual, while a change to github.com/fatedier/frp/pkg/virtual can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/virtual uses a module listed above it, which is the healthy direction.
38→21 github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/pkg/util/net✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/virtual uses a type in github.com/fatedier/frp/pkg/util/net.
- The types involved
github.com/fatedier/frp/pkg/virtual.Client→github.com/fatedier/frp/pkg/util/net.InternalListenergithub.com/fatedier/frp/pkg/virtual.pipeConnector→github.com/fatedier/frp/pkg/util/net.InternalListener
- Direction
- github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/pkg/util/net, so a change to github.com/fatedier/frp/pkg/util/net can break github.com/fatedier/frp/pkg/virtual, while a change to github.com/fatedier/frp/pkg/virtual can't break github.com/fatedier/frp/pkg/util/net.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/virtual uses a module listed above it, which is the healthy direction.
38→36 github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/client✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/virtual uses a type in github.com/fatedier/frp/client.
- The types involved
github.com/fatedier/frp/pkg/virtual.Client→github.com/fatedier/frp/client.Servicegithub.com/fatedier/frp/pkg/virtual.pipeConnector→github.com/fatedier/frp/client.Connector
- Direction
- github.com/fatedier/frp/pkg/virtual uses github.com/fatedier/frp/client, so a change to github.com/fatedier/frp/client can break github.com/fatedier/frp/pkg/virtual, while a change to github.com/fatedier/frp/pkg/virtual can't break github.com/fatedier/frp/client.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/virtual uses a module listed above it, which is the healthy direction.
39→9 github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/pkg/ssh uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/pkg/ssh.TunnelServer→github.com/fatedier/frp/pkg/config/v1.ClientCommonConfiggithub.com/fatedier/frp/pkg/ssh.ssh→github.com/fatedier/frp/pkg/config/v1.ProxyConfigurergithub.com/fatedier/frp/pkg/ssh.ssh→github.com/fatedier/frp/pkg/config/v1.SSHTunnelGateway
- Direction
- github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/pkg/ssh, while a change to github.com/fatedier/frp/pkg/ssh can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/ssh uses a module listed above it, which is the healthy direction.
39→21 github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/pkg/util/net✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/pkg/ssh uses a type in github.com/fatedier/frp/pkg/util/net.
- The types involved
github.com/fatedier/frp/pkg/ssh.Gateway→github.com/fatedier/frp/pkg/util/net.InternalListenergithub.com/fatedier/frp/pkg/ssh.TunnelServer→github.com/fatedier/frp/pkg/util/net.InternalListenergithub.com/fatedier/frp/pkg/ssh.ssh→github.com/fatedier/frp/pkg/util/net.InternalListener
- Direction
- github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/pkg/util/net, so a change to github.com/fatedier/frp/pkg/util/net can break github.com/fatedier/frp/pkg/ssh, while a change to github.com/fatedier/frp/pkg/ssh can't break github.com/fatedier/frp/pkg/util/net.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/ssh uses a module listed above it, which is the healthy direction.
39→30 github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/client/proxy✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/pkg/ssh uses a type in github.com/fatedier/frp/client/proxy.
- The types involved
github.com/fatedier/frp/pkg/ssh.TunnelServer→github.com/fatedier/frp/client/proxy.WorkingStatusgithub.com/fatedier/frp/pkg/ssh.ssh→github.com/fatedier/frp/client/proxy.WorkingStatus
- Direction
- github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/client/proxy, so a change to github.com/fatedier/frp/client/proxy can break github.com/fatedier/frp/pkg/ssh, while a change to github.com/fatedier/frp/pkg/ssh can't break github.com/fatedier/frp/client/proxy.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/ssh uses a module listed above it, which is the healthy direction.
39→38 github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/pkg/virtual✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/pkg/ssh uses a type in github.com/fatedier/frp/pkg/virtual.
- The types involved
github.com/fatedier/frp/pkg/ssh.TunnelServer→github.com/fatedier/frp/pkg/virtual.Client
- Direction
- github.com/fatedier/frp/pkg/ssh uses github.com/fatedier/frp/pkg/virtual, so a change to github.com/fatedier/frp/pkg/virtual can break github.com/fatedier/frp/pkg/ssh, while a change to github.com/fatedier/frp/pkg/ssh can't break github.com/fatedier/frp/pkg/virtual.
- Position
- Below the diagonal: github.com/fatedier/frp/pkg/ssh uses a module listed above it, which is the healthy direction.
40→3 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/proto/wire✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/proto/wire.
- The types involved
github.com/fatedier/frp/server.acceptedConnection→github.com/fatedier/frp/pkg/proto/wire.Conngithub.com/fatedier/frp/server.acceptedConnection→github.com/fatedier/frp/pkg/proto/wire.CryptoContextgithub.com/fatedier/frp/server.acceptedConnection→github.com/fatedier/frp/pkg/proto/wire.Frame
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/proto/wire, so a change to github.com/fatedier/frp/pkg/proto/wire can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/proto/wire.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→4 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/transport✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/transport.
- The types involved
github.com/fatedier/frp/server.Control→github.com/fatedier/frp/pkg/transport.MessageTransporter
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/transport, so a change to github.com/fatedier/frp/pkg/transport can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/transport.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→5 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/xlog✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/util/xlog.
- The types involved
github.com/fatedier/frp/server.Control→github.com/fatedier/frp/pkg/util/xlog.Logger
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/xlog, so a change to github.com/fatedier/frp/pkg/util/xlog can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/util/xlog.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→6 github.com/fatedier/frp/server uses github.com/fatedier/frp/server/metrics✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/server/metrics.
- The types involved
github.com/fatedier/frp/server.Control→github.com/fatedier/frp/server/metrics.ServerMetrics
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/server/metrics, so a change to github.com/fatedier/frp/server/metrics can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/server/metrics.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→9 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/config/v1✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/config/v1.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/pkg/config/v1.ServerConfiggithub.com/fatedier/frp/server.server→github.com/fatedier/frp/pkg/config/v1.ServerConfig
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/config/v1, so a change to github.com/fatedier/frp/pkg/config/v1 can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/config/v1.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→15 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/plugin/server✕
- Connections
- 3 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/plugin/server.
- The types involved
github.com/fatedier/frp/server.Control→github.com/fatedier/frp/pkg/plugin/server.UserInfogithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/plugin/server.Managergithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/pkg/plugin/server.Manager
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/plugin/server, so a change to github.com/fatedier/frp/pkg/plugin/server can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/plugin/server.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→17 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/http✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/util/http.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/util/http.RouterRegisterHelpergithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/util/http.Server
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/http, so a change to github.com/fatedier/frp/pkg/util/http can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/util/http.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→19 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/msg✕
- Connections
- 10 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/msg.
- The types involved
github.com/fatedier/frp/server.Control→github.com/fatedier/frp/pkg/msg.CloseProxygithub.com/fatedier/frp/server.Control→github.com/fatedier/frp/pkg/msg.Dispatchergithub.com/fatedier/frp/server.Control→github.com/fatedier/frp/pkg/msg.NewProxygithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/msg.NewVisitorConngithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/msg.NewWorkConngithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/pkg/msg.Conngithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/pkg/msg.Logingithub.com/fatedier/frp/server.acceptedConnection→github.com/fatedier/frp/pkg/msg.Conn
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/msg, so a change to github.com/fatedier/frp/pkg/msg can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/msg.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→21 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/net✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/util/net.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/util/net.InternalListener
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/net, so a change to github.com/fatedier/frp/pkg/util/net can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/util/net.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→22 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/vhost✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/util/vhost.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/util/vhost.Routers
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/util/vhost, so a change to github.com/fatedier/frp/pkg/util/vhost can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/util/vhost.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→25 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/auth✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/auth.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/auth.ServerAuthgithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/pkg/auth.Verifier
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/auth, so a change to github.com/fatedier/frp/pkg/auth can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/auth.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→31 github.com/fatedier/frp/server uses github.com/fatedier/frp/server/controller✕
- Connections
- 2 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/server/controller.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/server/controller.ResourceControllergithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/server/controller.ResourceController
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/server/controller, so a change to github.com/fatedier/frp/server/controller can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/server/controller.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→33 github.com/fatedier/frp/server uses github.com/fatedier/frp/server/proxy✕
- Connections
- 5 pairs of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/server/proxy.
- The types involved
github.com/fatedier/frp/server.Control→github.com/fatedier/frp/server/proxy.Proxygithub.com/fatedier/frp/server.Control→github.com/fatedier/frp/server/proxy.WorkConngithub.com/fatedier/frp/server.ControlManager→github.com/fatedier/frp/server/proxy.WorkConngithub.com/fatedier/frp/server.Service→github.com/fatedier/frp/server/proxy.Managergithub.com/fatedier/frp/server.SessionContext→github.com/fatedier/frp/server/proxy.Manager
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/server/proxy, so a change to github.com/fatedier/frp/server/proxy can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/server/proxy.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
40→39 github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/ssh✕
- Connections
- 1 pair of types, where a type in github.com/fatedier/frp/server uses a type in github.com/fatedier/frp/pkg/ssh.
- The types involved
github.com/fatedier/frp/server.Service→github.com/fatedier/frp/pkg/ssh.Gateway
- Direction
- github.com/fatedier/frp/server uses github.com/fatedier/frp/pkg/ssh, so a change to github.com/fatedier/frp/pkg/ssh can break github.com/fatedier/frp/server, while a change to github.com/fatedier/frp/server can't break github.com/fatedier/frp/pkg/ssh.
- Position
- Below the diagonal: github.com/fatedier/frp/server uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 34 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 25 | High / Critical |
| A02:2025 — Security Misconfiguration | 10 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Flaky test finding(s) in Test Reliability; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Add tests that import the unreached modules (directly or through their public entry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Flaky test finding(s) in Test Reliability. | +8.8 pts | Low | Test Reliability |
| Resolve the 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. | +4.0 pts | Low | Dependency Hygiene |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +5.0 pts | Medium | Dependency Hygiene |
| Add tests that import the unreached modules (directly or through their public entry). | +4.6 pts | Medium | Test 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.1 pts | Medium | Outbound HTTP resilience |
| Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED. | +1.5 pts | Low | Dependency Vulnerabilities |
| Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED, REDACTED. | +1.1 pts | Low | Dependency Vulnerabilities |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +1.7 pts | Medium | Keyboard semantics |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.6 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| pkg/config/legacy/client.go | 5.7 | Mixed | Cyclomatic Complexity: legacy.LoadAllProxyConfsFromIni (cyclomatic 19) |
| server/service.go | 6.0 | Mixed | Explicit Debt: TodoComment |
| pkg/config/source/store.go | 6.3 | Mixed | Code Duplication: Edited copy of a member (15 corresponding lines) |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 6.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| client/config_manager.go | 7.0 | Near-clean | Code Duplication: Edited copy of a member (31 corresponding lines) |
| server/http/controller.go | 7.0 | Near-clean | Code Duplication: Duplicated block (9 lines × 2) |
| web/frpc/src/types/proxy-converters.ts | 7.0 | Near-clean | Cyclomatic Complexity: proxy-converters.formToStoreProxy (cyclomatic 57) |
| client/http/controller.go | 7.0 | Near-clean | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| server/http/controller_v2.go | 7.0 | Near-clean | Cyclomatic Complexity: http.buildV2ProxySpec (cyclomatic 17) |
| client/proxy/sudp.go | 7.1 | Near-clean | Cyclomatic Complexity: SUDPProxy.InWorkConn (cyclomatic 17) |
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 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 64 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, 378 of 406 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
- D10 Test 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. The 14 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 168 test source file(s) (.go) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (154 contributor(s) across 1565 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 153 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `server/group/http.go`, `server/group/https.go`, `server/group/tcp.go`, `server/group/tcpmux.go` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go, Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- R4 Test Coverage — 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. 20 further occurrence(s) are not listed individually; the score already reflects all 60.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X21 Side-effecting pattern 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X26 Unsynchronised callback handoff — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's 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.
- X4 Structured logging — 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, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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
19 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was proxy-converters.formToStoreProxy at 57.
What to do
- Bring the 3 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with proxy-converters.formToStoreProxy (cyclomatic 57), proxy-converters.storeProxyToForm (cyclomatic 36), server.NewService (cyclomatic 33). — 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 3 together lifts Cyclomatic Complexity from 7.1 to about 7.8/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D2 · Cognitive Complexity
38 method(s) exceeded the cognitive complexity threshold of 15; the worst was proxy-converters.formToStoreProxy at 80.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with proxy-converters.formToStoreProxy (cognitive 80). — Refactoring it lifts Cognitive Complexity from 6.2 to about 6.5/10.
D3 · God Classes
6 god class(es) detected.
What to do
- Resolve the 2 TooManyFields finding(s) in God Classes — start with REDACTED, client.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with service.go, control.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with service.go. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
41 duplicated block group(s) detected. A further 45 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), udp_binary.go, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with root.go, feature_gate.go, plugin.go. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), auth.go, types.go. — One of this dimension's main actionable groups (5 warning-level).
D5 · Coupling
3 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
2 of 138 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with store.go, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 14 tests. Measured on the JavaScript/TypeScript suite only — at least 168 test source file(s) (.go) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
2 flaky across 2 measured tier(s). JavaScript/TypeScript (vitest via `npm ci --ignore-scripts` in web/ (15 tests)): measured (0 flaky); Go (github.com/fatedier/frp): measured (2 flaky).
What to do
- Resolve the 2 Flaky test finding(s) in Test Reliability. — One of this dimension's main actionable groups (2 issue-level).
D12 · Dependency Hygiene
10 outdated, 0 author-deprecated direct Go module(s), 2 pinning or checksum defect(s). 35 of 35 direct requirement(s) were graded against proxy.golang.org (0 not served there, 4 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 2 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 96 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 96 package(s) this repository's committed lockfile installs for a consumer — its 4 production, optional and peer dependency(ies), across 3 product REDACTED manifest(s), and everything those install in turn. Its 42 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: server/service.go (6×33=198); client/service.go (6×17=102)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with service.go (2). — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
2 deducted task-comment markers across 30969 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with service.go (2). — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 10 document(s) read across 5 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 3 build units (Go, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
67 % of calls cross a namespace and 13 % go through an interface, but 53 % 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)
34 finding(s): 0 critical, 18 high, 6 medium, 10 low. 9 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `server/group/http.go` (line 16), `server/group/https.go` (line 26), `server/group/tcp.go` (line 27), `server/group/tcpmux.go` (line 30) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 9 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (9 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
19 finding(s): 1 critical, 9 high, 9 medium, 0 low.
What to do
- Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- Resolve the 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
10 finding(s): 0 critical, 4 high, 6 medium, 0 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (6 warning-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 129 of the 243 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: client.go↔REDACTED 65%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with client.go. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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
AC2 · Forms & labels
AC3 · Page structure
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — web/frps/src/components/ClientCard.vue:2
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×2) — web/frps/src/views/ClientDetail.vue:5, web/frps/src/views/ProxyDetail.vue:5
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.badge` sets color: #888888 on background-color: #2a2a3e — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — web/frps/src/App.vue:225
- `.action-button .spinner` moves (`animation: spin 0.75s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — web/shared/components/ActionButton.vue:64
- `.popover-trigger.filterable-trigger .arrow-icon` moves (`transition: transform 0.2s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — web/shared/components/PopoverMenu.vue:275
- `.sidebar` moves (`transition: transform 0.25s cubic-bezier(0.4, 0, 0.2, 1)`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — web/frps/src/App.vue:506, web/frpc/src/App.vue:506
- `.arrow-icon` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — web/frps/src/components/StatCard.vue:104
- `.bar` moves (`transition: height 0.3s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — web/frps/src/components/Traffic.vue:203
- `.collapse-arrow` moves (`transition: transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — web/frpc/src/components/ConfigSection.vue:142
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- `web/frpc/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — web/frpc/package.json:15
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `http.Client{` 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. (×3) — REDACTED:76, REDACTED:48, REDACTED:50
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.
PF1 · Benchmark discipline
- A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — server/proxy/sudp_benchmark_test.go
What to do
- Call b.ReportAllocs() in the benchmarks, or run them with `go test -bench . -benchmem`, so allocation regressions are visible, not just time.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 5 duplicated blocks under web/ have copies in at least two of the sibling directories frpc, frps — 4 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — web/frpc/vite.config.mts:12
- web/frpc/src/views/ProxyEdit.vue:59 · web/frpc/src/views/VisitorEdit.vue:58 — the two spans are one implementation copied and then locally edited — 683 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frpc/src/views/ProxyEdit.vue:59
- web/frps/src/views/ClientDetail.vue:180 · web/frps/src/views/Proxies.vue:128 — the two spans are one implementation copied and then locally edited — 394 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frps/src/views/ClientDetail.vue:180
- web/frpc/vite.config.mts:12 · web/frps/vite.config.mts:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — web/frpc/vite.config.mts:12
- web/frps/src/views/Clients.vue:110 · web/frps/src/views/Proxies.vue:221 — the two spans are one implementation copied and then locally edited — 190 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frps/src/views/Clients.vue:110
- web/frpc/src/views/ProxyList.vue:226 · web/frpc/src/views/VisitorList.vue:115 — the two spans are one implementation copied and then locally edited — 216 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frpc/src/views/ProxyList.vue:226
- web/frpc/src/stores/proxy.ts:42 · web/frpc/src/stores/visitor.ts:18 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — web/frpc/src/stores/proxy.ts:42
- web/frpc/src/api/http.ts:44 · web/frpc/src/api/http.ts:67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — web/frpc/src/api/http.ts:44
- web/frpc/src/types/proxy-converters.ts:255 · web/frpc/src/types/proxy-converters.ts:300 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frpc/src/types/proxy-converters.ts:255
- web/frpc/src/utils/format.ts:1 · web/frps/src/utils/format.ts:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — web/frpc/src/utils/format.ts:1
- web/frpc/src/App.vue:90 · web/frps/src/App.vue:102 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — web/frpc/src/App.vue:90
- web/frpc/src/api/http.ts:14 · web/frps/src/api/http.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frpc/src/api/http.ts:14
- web/frps/src/utils/proxy.ts:87 · web/frps/src/utils/proxy.ts:113 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frps/src/utils/proxy.ts:87
- web/frps/src/views/ClientDetail.vue:309 · web/frps/src/views/Clients.vue:131 · web/frps/src/views/Proxies.vue:245 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frps/src/views/ClientDetail.vue:309
- web/frps/src/views/ClientDetail.vue:327 · web/frps/src/views/Clients.vue:144 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frps/src/views/ClientDetail.vue:327
- web/frps/src/api/client.ts:5 · web/frps/src/api/proxy.ts:21 — the two spans are one implementation copied and then locally edited — 68 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frps/src/api/client.ts:5
- web/frpc/src/components/proxy-form/ProxyBackendSection.vue:84 · web/frpc/src/components/visitor-form/VisitorPluginSection.vue:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frpc/src/components/proxy-form/ProxyBackendSection.vue:84
- web/frps/src/utils/proxy.ts:64 · web/frps/src/utils/proxy.ts:78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — web/frps/src/utils/proxy.ts:64
- web/frpc/src/components/proxy-form/ProxyBaseSection.vue:35 · web/frpc/src/components/visitor-form/VisitorBaseSection.vue:24 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — web/frpc/src/components/proxy-form/ProxyBaseSection.vue:35
- web/frpc/src/components/proxy-form/ProxyBaseSection.vue:35 · web/frpc/src/components/proxy-form/ProxyFormLayout.vue:38 · web/frpc/src/components/visitor-form/VisitorBaseSection.vue:24 · web/frpc/src/components/visitor-form/VisitorFormLayout.vue:27 — the 4 copies are spread across 4 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — web/frpc/src/components/proxy-form/ProxyBaseSection.vue:35
- web/frpc/src/views/ProxyDetail.vue:77 · web/frpc/src/views/VisitorDetail.vue:55 — the two spans are one implementation copied and then locally edited — 61 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frpc/src/views/ProxyDetail.vue:77
- web/frps/src/views/ClientDetail.vue:167 · web/frps/src/views/ProxyDetail.vue:267 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frps/src/views/ClientDetail.vue:167
- web/frpc/src/components/proxy-form/ProxyAuthSection.vue:25 · web/frpc/src/components/proxy-form/ProxyHealthSection.vue:28 · web/frpc/src/components/proxy-form/ProxyHttpSection.vue:17 · web/frpc/src/components/proxy-form/ProxyLoadBalanceSection.vue:16 · +6 more site(s) not listed — the 10 copies are spread across 10 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — web/frpc/src/components/proxy-form/ProxyAuthSection.vue:25
- web/frpc/src/components/proxy-form/ProxyFormLayout.vue:38 · web/frpc/src/components/proxy-form/ProxyRemoteSection.vue:26 — the two spans are one implementation copied and then locally edited — 73 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — web/frpc/src/components/proxy-form/ProxyFormLayout.vue:38
- web/frpc/src/types/proxy-converters.ts:395 · web/frpc/src/types/proxy-converters.ts:424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — web/frpc/src/types/proxy-converters.ts:395
- web/frpc/src/views/ProxyList.vue:184 · web/frpc/src/views/ProxyList.vue:191 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frpc/src/views/ProxyList.vue:184
- web/frps/src/views/ClientDetail.vue:289 · web/frps/src/views/Clients.vue:110 · web/frps/src/views/Proxies.vue:221 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — web/frps/src/views/ClientDetail.vue:289
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- formToStoreProxy has cyclomatic complexity 57 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/types/proxy-converters.ts:10
- storeProxyToForm has cyclomatic complexity 36 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/types/proxy-converters.ts:328
- formToStoreVisitor has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/types/proxy-converters.ts:170
- storeVisitorToForm has cyclomatic complexity 18 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/types/proxy-converters.ts:438
- getStoreProxyBlock has cyclomatic complexity 17 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/types/proxy-converters.ts:243
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — web/frps/src/views/ClientDetail.vue:219, web/frps/src/views/Proxies.vue:152
- fetchProxy has cyclomatic complexity 15 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frps/src/views/ProxyDetail.vue:356
- fetchData has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frps/src/views/Proxies.vue:211
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/views/ProxyDetail.vue:90
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frpc/src/stores/proxy.ts:91
- fetchProxies has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/frps/src/views/ClientDetail.vue:277
R3 · Large Files
- web/frps/src/views/ProxyDetail.vue has 725 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frps/src/views/ProxyDetail.vue:1
- web/frps/src/views/ClientDetail.vue has 563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frps/src/views/ClientDetail.vue:1
- web/frpc/src/App.vue has 450 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frpc/src/App.vue:1
- web/frps/src/App.vue has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frps/src/App.vue:1
- web/frpc/src/types/proxy-converters.ts has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frpc/src/types/proxy-converters.ts:1
- web/frps/src/views/Proxies.vue has 414 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frps/src/views/Proxies.vue:1
- web/frps/src/views/ServerOverview.vue has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/frps/src/views/ServerOverview.vue:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — web/frps/src/views/ProxyDetail.vue:1, web/frps/src/views/ClientDetail.vue:1, web/frps/src/views/Proxies.vue:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 7 file(s) (~566 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — web/shared
- Unreachable from the 17 application, 13 tooling and 6 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (17 application, 13 tooling, 6 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — web/frpc/src/utils/format.ts
- Nothing ultimately consumes this binding: its only referrer is the re-export in web/frpc/src/types/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in web/frpc/src/types/index.ts in the same commit, or the barrel will import a name that no longer exists. — web/frpc/src/types/constants.ts:32
- Nothing imports this binding — it is safe to review for removal. (×5) — web/frps/src/api/client.ts:5, web/frps/src/api/client.ts:24, web/frps/src/api/proxy.ts:21, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×4) — web/frpc/src/App.vue:85, web/frps/src/App.vue:97, web/shared/components/FilterDropdown.vue:30, …
- Declared in web/frpc/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in web/frps/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X2 · Cancellation propagation
- Only 14/15 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `SetDefaultDNSAddress` calls `net.Dial(…)` 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/util/net/dns.go:22
What to do
- Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
X26 · Unsynchronised callback handoff
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — web/frpc/src/views/ProxyDetail.vue:101, web/frpc/src/views/ProxyDetail.vue:109, web/frpc/src/views/VisitorDetail.vue:75, …
- `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. (×26) — server/proxy/proxy.go:289, server/ports/ports.go:159, server/ports/ports.go:163, …
- `if errRet != 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. — server/proxy/xtcp.go:74
- `if err := errors.PanicToError(func() { ch <- m }); 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. — pkg/transport/message.go:94
- `if err := ssh.Unmarshal(req.Payload, &payload); 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. — pkg/ssh/server.go:217
- `if err := ssh.Unmarshal(payload, &msg); 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. — pkg/ssh/server.go:337
- `if err = errors.PanicToError(func() { select { case sendCh <- udpMsg: default: } }); 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/proto/udp/udp.go:66, pkg/proto/udp/udp.go:101
- `if err := errors.PanicToError(func() { clientCfg.sidCh <- sid }); 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. — REDACTED:208
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- 2/4 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Strong | Solid. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 81% | Strong | Solid. |
| Readiness | 41% | Weak — gated by R4, R8, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 65% | Adequate — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 91% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 57 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- 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; this repository's TypeScript 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — no exported interface declares behaviour
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no REDACTED in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read REDACTED: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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 — Naming consistency is measured on C# and TypeScript only; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — web/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): a Domain/Aggregates/ValueObjects layer
- 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 and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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 — X1 reached only 26% of this repository's production lines — go (29,147 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 26% of this repository's production lines — go (29,147 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — X21 reached only 26% of this repository's production lines — go (29,147 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — 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 — 39 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
- Unlisted import '@element-plus/icons-vue' web/frpc/src/App.vue:85
- Unlisted import '@element-plus/icons-vue' web/frps/src/App.vue:97
- Unlisted import '@element-plus/icons-vue' web/shared/components/FilterDropdown.vue:30
- Flaky test: .::github.com/fatedier/frp/server.TestNewServiceReleasesListenersOnWebServerFailure
- Flaky test: .::github.com/fatedier/frp/server.TestNewServiceReleasesListenersOnWebServerFailure/invalid_TLS_certificate
- REDACTED
- REDACTED
- Click handler on a non-interactive <div> web/frps/src/components/ClientCard.vue:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'element-plus' web/shared/components/PopoverMenu.vue:75
Serious — 323 finding(s)
- No test reaches this file web/frps/src/views/ProxyDetail.vue:1
- No test reaches this file web/frps/src/views/ClientDetail.vue:1
- No test reaches this file web/frps/src/views/Proxies.vue:1
- No test reaches this file web/frpc/src/views/ProxyList.vue:1
- No test reaches this file web/frpc/src/views/VisitorEdit.vue:1
- No test reaches this file web/frps/src/views/ServerOverview.vue:1
- No test reaches this file web/frpc/src/views/ProxyEdit.vue:1
- No test reaches this file web/frps/src/views/Clients.vue:1
- No test reaches this file web/frpc/src/views/VisitorList.vue:1
- No test reaches this file web/frps/src/utils/proxy.ts:1
- No test reaches this file web/frpc/src/views/ProxyDetail.vue:1
- No test reaches this file web/frpc/src/components/proxy-form/ProxyBackendSection.vue:1
- No test reaches this file web/frpc/src/stores/proxy.ts:1
- No test reaches this file web/frps/src/App.vue:1
- No test reaches this file web/frps/src/api/http.ts:1
- No test reaches this file web/frps/src/api/proxy.ts:1
- No test reaches this file web/frps/src/components/Traffic.vue:1
- No test reaches this file web/frpc/src/App.vue:1
- No test reaches this file web/frpc/src/views/ClientConfigure.vue:1
- No test reaches this file web/frpc/src/components/ProxyCard.vue:1
- No test reaches this file web/frpc/src/views/VisitorDetail.vue:1
- No test reaches this file web/frpc/src/api/frpc.ts:1
- No test reaches this file web/frpc/src/api/http.ts:1
- No test reaches this file web/frpc/src/router/index.ts:1
- No test reaches this file web/frpc/src/components/ConfigSection.vue:1
- Swallowed exception (caught, then discarded) server/proxy/proxy.go:289
- Swallowed exception (caught, then discarded) server/proxy/xtcp.go:74
- Swallowed exception (caught, then discarded) server/ports/ports.go:159
- Swallowed exception (caught, then discarded) server/ports/ports.go:163
- Swallowed exception (caught, then discarded) server/ports/ports.go:171
- Swallowed exception (caught, then discarded) server/group/base.go:40
- Swallowed exception (caught, then discarded) pkg/vnet/tun.go:41
- Swallowed exception (caught, then discarded) pkg/util/vhost/vhost.go:161
- Swallowed exception (caught, then discarded) pkg/util/system/system_android.go:33
- Swallowed exception (caught, then discarded) pkg/util/system/system_android.go:37
- Swallowed exception (caught, then discarded) pkg/util/log/log.go:63
- Swallowed exception (caught, then discarded) pkg/transport/message.go:94
- Swallowed exception (caught, then discarded) pkg/ssh/gateway.go:108
- Swallowed exception (caught, then discarded) pkg/ssh/gateway.go:123
- Swallowed exception (caught, then discarded) pkg/ssh/server.go:152
- Swallowed exception (caught, then discarded) pkg/ssh/server.go:217
- Swallowed exception (caught, then discarded) pkg/ssh/server.go:307
- Swallowed exception (caught, then discarded) pkg/ssh/server.go:337
- Swallowed exception (caught, then discarded) pkg/ssh/server.go:351
- Swallowed exception (caught, then discarded) pkg/proto/udp/udp.go:48
- Swallowed exception (caught, then discarded) pkg/proto/udp/udp.go:60
- Swallowed exception (caught, then discarded) pkg/proto/udp/udp.go:66
- Swallowed exception (caught, then discarded) pkg/proto/udp/udp.go:96
- Swallowed exception (caught, then discarded) pkg/proto/udp/udp.go:101
- Swallowed exception (caught, then discarded) pkg/proto/udp/udp.go:116
- Animation without a prefers-reduced-motion guard web/shared/components/ActionButton.vue:64
- Animation without a prefers-reduced-motion guard web/shared/components/PopoverMenu.vue:275
- Animation without a prefers-reduced-motion guard web/frps/src/App.vue:506
- Animation without a prefers-reduced-motion guard web/frps/src/components/StatCard.vue:104
- Animation without a prefers-reduced-motion guard web/frps/src/components/Traffic.vue:203
- Animation without a prefers-reduced-motion guard web/frpc/src/App.vue:506
- Animation without a prefers-reduced-motion guard web/frpc/src/components/ConfigSection.vue:142
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) client/http/controller.go:243
- Duplicated block (7 lines × 2) client/http/controller.go:359
- Duplicated block (7 lines × 2) pkg/msg/udp_binary.go:304
- Duplicated block (7 lines × 2) server/proxy/http.go:137
- Duplicated block (7 lines × 2) client/proxy/sudp.go:60
- Duplicated block (7 lines × 2) pkg/config/load.go:429
- Edited copy of a member (9 corresponding lines) cmd/frpc/sub/root.go:49
- Edited copy of a member (9 corresponding lines) pkg/policy/featuregate/feature_gate.go:162
- Edited copy of a member (9 corresponding lines) pkg/plugin/client/plugin.go:31
- Edited copy of a member (9 corresponding lines) client/api_router.go:79
- Edited copy of a member (9 corresponding lines) client/visitor/visitor_manager.go:191
- Duplicated block (11 lines × 2) client/http/controller.go:249
- Duplicated block (11 lines × 2) client/http/controller.go:284
- Duplicated block (11 lines × 2) pkg/auth/auth.go:43
- Duplicated block (11 lines × 2) pkg/config/types/types.go:140
- Duplicated block (11 lines × 2) server/proxy/tcp.go:37
- Edited copy of a member (20 corresponding lines) pkg/config/legacy/parse.go:68
- Edited copy of a member (20 corresponding lines) client/config_manager.go:251
- Edited copy of a member (20 corresponding lines) server/group/http.go:137
- Edited copy of a member (20 corresponding lines) client/config_manager.go:102
- Edited copy of a member (12 corresponding lines) pkg/msg/udp_binary.go:286
- Edited copy of a member (12 corresponding lines) server/http/controller_v2.go:269
- Edited copy of a member (12 corresponding lines) client/visitor/xtcp.go:376
- Edited copy of a member (12 corresponding lines) pkg/config/legacy/proxy.go:375
- Duplicated block (13 lines × 2) server/proxy/proxy.go:459
- Duplicated block (13 lines × 2) pkg/util/net/kcp.go:80
- Duplicated block (13 lines × 2) client/config_manager.go:205
- Duplicated block (13 lines × 2) client/config_manager.go:258
- Duplicated block (9 lines × 2) server/http/controller.go:118
- Duplicated block (9 lines × 2) client/service.go:48
- Duplicated block (9 lines × 2) pkg/config/v1/proxy.go:252
- Duplicated block (9 lines × 2) pkg/plugin/client/plugin.go:100
- Duplicated block (6 lines × 2) pkg/config/legacy/parse.go:82
- Duplicated block (6 lines × 2) cmd/frpc/sub/root.go:108
- Duplicated block (6 lines × 2) pkg/plugin/client/plugin.go:41
- Duplicated block (6 lines × 2) client/visitor/stcp.go:35
- Duplicated block (15 lines × 2 locations) web/frpc/src/App.vue:90
- Duplicated block (15 lines × 2 locations) web/frpc/src/api/http.ts:14
- Duplicated block (15 lines × 2 locations) web/frps/src/utils/proxy.ts:87
- Duplicated block (15 lines × 2 locations) web/frps/src/views/ClientDetail.vue:327
- Swallowed exception (empty catch) web/frpc/src/views/ProxyDetail.vue:101
- Swallowed exception (empty catch) web/frpc/src/views/ProxyDetail.vue:109
- Swallowed exception (empty catch) web/frpc/src/views/VisitorDetail.vue:75
- Swallowed exception (empty catch) pkg/util/net/udp.go:71
- Edited copy of a member (15 corresponding lines) pkg/sdk/client/client.go:35
- Edited copy of a member (15 corresponding lines) pkg/config/source/store.go:226
- Edited copy of a member (15 corresponding lines) pkg/plugin/client/http_proxy.go:50
- Duplicated block (10 lines × 2) pkg/config/legacy/value.go:27
- Duplicated block (10 lines × 2) client/proxy/udp.go:51
- Duplicated block (10 lines × 2) pkg/config/v1/proxy.go:201
- Outbound HTTP without resilience REDACTED:76
- Outbound HTTP without resilience REDACTED:48
- Outbound HTTP without resilience REDACTED:50
- Anchor without href web/frps/src/views/ClientDetail.vue:5
- Anchor without href web/frps/src/views/ProxyDetail.vue:5
- Dependency pinned to a stale untagged commit: github.com/armon/go-socks5
- Dependency pinned to a stale untagged commit: github.com/songgao/water
- Hotspot: server/service.go server/service.go:148
- Hotspot: client/service.go client/service.go:247
- TodoComment server/service.go:765
- TodoComment server/service.go:982
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TooManyFields: ServerCommonConf pkg/config/legacy/server.go:36
- TooManyFields: ClientCommonConf pkg/config/legacy/client.go:34
- FileTooLong: server/service.go server/service.go
- FileTooLong: server/control.go server/control.go
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) cmd/frpc/sub/proxy.go:73
- Edited copy of a member (31 corresponding lines) client/config_manager.go:219
- Edited copy of a member (22 corresponding lines) pkg/util/http/handler.go:39
- Edited copy of a member (22 corresponding lines) client/config_manager.go:412
- Edited copy of a member (26 corresponding lines) pkg/config/v1/decode.go:100
- Edited copy of a member (26 corresponding lines) pkg/config/v1/validation/proxy.go:103
- Edited copy of a member (21 corresponding lines) client/config_manager.go:197
- Edited copy of a member (21 corresponding lines) server/proxy/proxy.go:458
- Edited copy of a member (17 corresponding lines) pkg/auth/auth.go:42
- Edited copy of a member (17 corresponding lines) pkg/config/legacy/proxy.go:78
- Edited copy of a member (11 corresponding lines) cmd/frpc/sub/admin.go:75
- Edited copy of a member (11 corresponding lines) client/http/model/proxy_definition.go:45
- Edited copy of a member (10 corresponding lines) pkg/vnet/controller.go:377
- Edited copy of a member (10 corresponding lines) pkg/config/source/store.go:287
- Duplicated block (14 lines × 2) client/config_manager.go:413
- Duplicated block (14 lines × 2) client/config_manager.go:236
- Duplicated block (12 lines × 2) pkg/sdk/client/client.go:36
- Duplicated block (12 lines × 2) pkg/util/http/handler.go:40
- Duplicated block (8 lines × 2) pkg/config/legacy/conversion.go:27
- Duplicated block (8 lines × 2) pkg/plugin/client/plugin.go:48
- Duplicated block (5 lines × 2) client/api_router.go:60
- Duplicated block (5 lines × 2) pkg/plugin/client/https2http.go:42
- Low cohesion: StoreSource (LCOM4 9) pkg/config/source/store.go:36
- Low cohesion: Controller (LCOM4 6) server/http/controller.go:36
- Duplicated block (23 lines × 2 locations) web/frpc/src/api/http.ts:44
- Duplicated block (23 lines × 2 locations) web/frpc/src/types/proxy-converters.ts:255
- Duplicated block (11 lines × 2 locations) web/frpc/src/components/proxy-form/ProxyBackendSection.vue:84
- Duplicated block (11 lines × 2 locations) web/frps/src/utils/proxy.ts:64
- Duplicated block (10 lines × 2 locations) web/frpc/src/components/proxy-form/ProxyBaseSection.vue:35
- Duplicated block (10 lines × 2 locations) web/frps/src/views/ClientDetail.vue:167
- Complex function (anonymous) (cyclomatic 15, cognitive 17) web/frps/src/views/ClientDetail.vue:219
- Complex function (anonymous) (cyclomatic 15, cognitive 17) web/frps/src/views/Proxies.vue:152
- Unused dependency '@vue/tsconfig'
- Unused dependency '@vue/tsconfig'
- Low contrast colour pair in CSS (4.0:1) web/frps/src/App.vue:225
- proxy-converters.formToStoreProxy (cyclomatic 57) web/frpc/src/types/proxy-converters.ts:10
- proxy-converters.storeProxyToForm (cyclomatic 36) web/frpc/src/types/proxy-converters.ts:328
- server.NewService (cyclomatic 33) server/service.go:148
- UDPProxy.Run (cyclomatic 27) server/proxy/udp.go:78
- proxy-converters.formToStoreVisitor (cyclomatic 24) web/frpc/src/types/proxy-converters.ts:170
- nathole.MakeHole (cyclomatic 23) REDACTED:192
- legacy.LoadAllProxyConfsFromIni (cyclomatic 19) pkg/config/legacy/client.go:204
- BaseProxy.HandleTCPWorkConnection (cyclomatic 18) client/proxy/proxy.go:173
- proxy-converters.storeVisitorToForm (cyclomatic 18) web/frpc/src/types/proxy-converters.ts:438
- SUDPProxy.InWorkConn (cyclomatic 17) client/proxy/sudp.go:79
- Service.Run (cyclomatic 17) client/service.go:247
- http.buildV2ProxySpec (cyclomatic 17) server/http/controller_v2.go:564
- proxy-converters.getStoreProxyBlock (cyclomatic 17) web/frpc/src/types/proxy-converters.ts:243
- controlSessionDialer.exchangeLogin (cyclomatic 16) client/control_session.go:136
- nathole.ClassifyNATFeature (cyclomatic 16) pkg/nathole/classify.go:42
- Controller.APIV2ClientList (cyclomatic 16) server/http/controller_v2.go:143
- ClientRegistry.RegisterWithControlID (cyclomatic 16) server/registry/registry.go:74
- Service.handleConnection (cyclomatic 16) server/service.go:524
- Service.RegisterControl (cyclomatic 16) server/service.go:848
- proxy-converters.formToStoreProxy (cognitive 80) web/frpc/src/types/proxy-converters.ts:10
- server.NewService (cognitive 50) server/service.go:148
- UDPProxy.Run (cognitive 48) server/proxy/udp.go:78
- nathole.MakeHole (cognitive 37) REDACTED:192
- proxy-converters.storeProxyToForm (cognitive 35) web/frpc/src/types/proxy-converters.ts:328
- Service.handleConnection (cognitive 33) server/service.go:524
- proxy-converters.formToStoreVisitor (cognitive 32) web/frpc/src/types/proxy-converters.ts:170
- Manager.Acquire (cognitive 31) server/ports/ports.go:82
- config.LoadAdditionalClientConfigs (cognitive 27) pkg/config/load.go:502
- legacy.LoadAllProxyConfsFromIni (cognitive 26) pkg/config/legacy/client.go:204
- udp.Forwarder (cognitive 26) pkg/proto/udp/udp.go:77
- ControlManager.Add (cognitive 26) server/control.go:110
- controlSessionDialer.exchangeLogin (cognitive 23) client/control_session.go:136
- Controller.readLoopServer (cognitive 23) pkg/vnet/controller.go:193
- SUDPProxy.InWorkConn (cognitive 22) client/proxy/sudp.go:79
- Service.Run (cognitive 22) client/service.go:247
- config.LoadClientConfigResult (cognitive 22) pkg/config/load.go:346
- BaseProxy.startCommonTCPListenersHandler (cognitive 22) server/proxy/proxy.go:232
- Service.HandleListener (cognitive 22) server/service.go:766
- SUDPVisitor.worker (cognitive 21) client/visitor/sudp.go:113
- BaseProxy.HandleTCPWorkConnection (cognitive 20) client/proxy/proxy.go:173
- nathole.ClassifyNATFeature (cognitive 20) pkg/nathole/classify.go:42
- fastBackoffImpl.Backoff (cognitive 20) REDACTED:77
- Controller.APIV2ClientList (cognitive 20) server/http/controller_v2.go:143
- legacy.getIncludeContents (cognitive 19) pkg/config/legacy/parse.go:68
- VirtualNetPlugin.run (cognitive 19) pkg/plugin/visitor/virtual_net.go:116
- Service.Run (cognitive 19) server/service.go:403
- util.ParseRangeNumbers (cognitive 18) REDACTED:67
- Wrapper.checkWorker (cognitive 17) client/proxy/proxy_wrapper.go:196
- ClientCommonConf.Validate (cognitive 17) pkg/config/legacy/client.go:362
- vhost.NewHTTPReverseProxy (cognitive 17) pkg/util/vhost/http.go:49
- http.buildV2ProxySpec (cognitive 17) server/http/controller_v2.go:564
- HTTPProxy.Run (cognitive 17) server/proxy/http.go:55
- Service.RegisterControl (cognitive 17) server/service.go:848
- proxy-converters.storeVisitorToForm (cognitive 17) web/frpc/src/types/proxy-converters.ts:438
- TunnelServer.waitForwardAddrAndExtraPayload (cognitive 16) pkg/ssh/server.go:203
- Controller.APIV2ProxyList (cognitive 16) server/http/controller_v2.go:221
- ClientRegistry.RegisterWithControlID (cognitive 16) server/registry/registry.go:74
- REDACTED
- REDACTED
- FunctionTooLong: server.NewService server/service.go:148
- MethodTooLong: UDPProxy.Run server/proxy/udp.go:78
- Change coupling: client.go ↔ REDACTED pkg/config/legacy/client.go:1
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) client/http/controller.go:242
- Edited copy of a member (84 corresponding lines) client/proxy/sudp.go:79
- Edited copy of a member (46 corresponding lines) server/http/controller_v2.go:143
- Edited copy of a member (33 corresponding lines) server/group/https.go:70
- Edited copy of a member (37 corresponding lines) pkg/config/types/types.go:137
- Edited copy of a member (27 corresponding lines) pkg/config/v1/decode.go:44
- Edited copy of a member (28 corresponding lines) client/proxy/xtcp.go:142
- Edited copy of a member (19 corresponding lines) client/http/controller.go:203
- Edited copy of a member (25 corresponding lines) pkg/plugin/client/https2http.go:35
- Edited copy of a member (23 corresponding lines) REDACTED:91
- Edited copies of one member (4 members, 17+ corresponding lines) client/http/controller.go:166
- Edited copy of a member (18 corresponding lines) pkg/metrics/text/text.go:118
- Edited copy of a member (16 corresponding lines) client/config_manager.go:180
- Edited copy of a member (13 corresponding lines) pkg/config/v1/proxy.go:329
- Edited copies of one member (3 members, 9+ corresponding lines) client/proxy/proxy_manager.go:123
- Duplicated block (19 lines × 2) client/proxy/xtcp.go:63
- Duplicated block (17–18 lines × 2) client/http/model/proxy_definition.go:122
- Duplicated block (15–16 lines × 2) cmd/frpc/sub/proxy.go:77
- Duplicated block (15 lines × 2) pkg/proto/udp/udp.go:60
- Duplicated block (9–10 lines × 2) client/proxy/sudp.go:83
- Duplicated block (6 lines × 4) client/http/controller.go:254
- Duplicated block (10 lines × 5) server/proxy/http.go:44
- Coverage not measured — JavaScript/TypeScript suite
- Coverage collected but not gated
- Duplication concentrated across 2 sibling directories (5 clone groups) web/frpc/vite.config.mts:12
- Duplicated block with local edits (126 matched lines × 2 locations) web/frpc/src/views/ProxyEdit.vue:59
- Duplicated block with local edits (74 matched lines × 2 locations) web/frps/src/views/ClientDetail.vue:180
- Duplicated block (45 lines × 2 locations) web/frpc/vite.config.mts:12
- Duplicated block with local edits (37 matched lines × 2 locations) web/frps/src/views/Clients.vue:110
- Duplicated block with local edits (36 matched lines × 2 locations) web/frpc/src/views/ProxyList.vue:226
- Duplicated block (33 lines × 2 locations) web/frpc/src/stores/proxy.ts:42
- Duplicated block (20 lines × 2 locations) web/frpc/src/utils/format.ts:1
- Duplicated block (15 lines × 3 locations) web/frps/src/views/ClientDetail.vue:309
- Duplicated block with local edits (13 matched lines × 2 locations) web/frps/src/api/client.ts:5
- Duplicated block (10 lines × 4 locations) web/frpc/src/components/proxy-form/ProxyBaseSection.vue:35
- Duplicated block with local edits (10 matched lines × 2 locations) web/frpc/src/views/ProxyDetail.vue:77
- Duplicated block (9 lines × 10 locations) web/frpc/src/components/proxy-form/ProxyAuthSection.vue:25
- Duplicated block with local edits (9 matched lines × 2 locations) web/frpc/src/components/proxy-form/ProxyFormLayout.vue:38
- Duplicated block (7 lines × 2 locations) web/frpc/src/types/proxy-converters.ts:395
- Duplicated block (5 lines × 2 locations) web/frpc/src/views/ProxyList.vue:184
- Duplicated block (5 lines × 3 locations) web/frps/src/views/ClientDetail.vue:289
- Complex function formToStoreProxy (cyclomatic 57, cognitive 81) web/frpc/src/types/proxy-converters.ts:10
- Complex function storeProxyToForm (cyclomatic 36, cognitive 25) web/frpc/src/types/proxy-converters.ts:328
- Complex function formToStoreVisitor (cyclomatic 24, cognitive 32) web/frpc/src/types/proxy-converters.ts:170
- Complex function storeVisitorToForm (cyclomatic 18, cognitive 11) web/frpc/src/types/proxy-converters.ts:438
- Complex function getStoreProxyBlock (cyclomatic 17, cognitive 9) web/frpc/src/types/proxy-converters.ts:243
- Complex function fetchProxy (cyclomatic 15, cognitive 14) web/frps/src/views/ProxyDetail.vue:356
- Complex function fetchData (cyclomatic 12, cognitive 11) web/frps/src/views/Proxies.vue:211
- Complex function (anonymous) (cyclomatic 11, cognitive 14) web/frpc/src/views/ProxyDetail.vue:90
- Complex function (anonymous) (cyclomatic 11, cognitive 10) web/frpc/src/stores/proxy.ts:91
- Complex function fetchProxies (cyclomatic 11, cognitive 10) web/frps/src/views/ClientDetail.vue:277
- web/frps/src/views/ProxyDetail.vue: 725 lines of code web/frps/src/views/ProxyDetail.vue:1
- web/frps/src/views/ClientDetail.vue: 563 lines of code web/frps/src/views/ClientDetail.vue:1
- web/frpc/src/App.vue: 450 lines of code web/frpc/src/App.vue:1
- web/frps/src/App.vue: 449 lines of code web/frps/src/App.vue:1
- web/frpc/src/types/proxy-converters.ts: 429 lines of code web/frpc/src/types/proxy-converters.ts:1
- web/frps/src/views/Proxies.vue: 414 lines of code web/frps/src/views/Proxies.vue:1
- web/frps/src/views/ServerOverview.vue: 404 lines of code web/frps/src/views/ServerOverview.vue:1
- Dead file (~33 LoC) web/frpc/src/utils/format.ts
- Function without context.Context: SetDefaultDNSAddress pkg/util/net/dns.go:22
Minor — 34 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate server/http/controller.go:106
- Duplicated predicate client/http/model/proxy_definition.go:31
- Duplicated predicate server/http/controller.go:109
- Duplicated predicate web/frps/src/api/client.ts:15
- Pending state with no failure state web/frps/src/views/ClientDetail.vue:16
- Pending state with no failure state web/frps/src/views/ClientDetail.vue:99
- No ADRs found cmd/frps/main.go:15
- Projects may be oversized for their cohesion
- Scattered collaborators
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No dependency-update automation web/frpc/package.json:15
- Benchmarks don't track allocations server/proxy/sudp_benchmark_test.go
- Unused export 'PluginType' web/frpc/src/types/constants.ts:32
- Unused export 'getClients' web/frps/src/api/client.ts:5
- Unused export 'getClient' web/frps/src/api/client.ts:24
- Unused export 'getProxiesByType' web/frps/src/api/proxy.ts:21
- Unused export 'getProxy' web/frps/src/api/proxy.ts:93
- Unused export 'getProxyByName' web/frps/src/api/proxy.ts:104
- Not all functions that make a request accept a context.Context or an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 10 finding(s)
- Outdated: github.com/pires/go-proxyproto
- Outdated: github.com/prometheus/common
- Outdated: github.com/spf13/pflag
- Outdated: github.com/tidwall/gjson
- Outdated: github.com/xtaci/kcp-go/v5
- Outdated: golang.org/x/crypto
- Outdated: golang.org/x/oauth2
- Outdated: golang.org/x/sync
- Outdated: golang.org/x/sys
- Outdated: gopkg.in/ini.v1
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-413555666da74894a705a5d43e86e5d3/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-413555666da74894a705a5d43e86e5d3/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 . | 34 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 19 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 10 | 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. semgrep could not parse 4 file(s) — `server/group/http.go`, `server/group/https.go`, `server/group/tcp.go`, `server/group/tcpmux.go` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |