Executive summary
grpc/grpc-web falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 43 out of 100 and is rated Weak, and 34 of its 38 critical findings are security problems.
Production Readiness, at 29, is the weakest lens and counts most in the score. The best first steps are adopting a logging library and adding automated security scanning, each worth about 5 points. Raising Production Readiness to 70 would lift the score to about 56.
Seventeen settings leave the servers or containers unsafe. Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Correcting the unsafe settings and pinning each tool to an exact version would close both risks. Updating the vulnerable packages would fix the three packages with a known security hole, and passing outside input through environment variables would deal with the three pipeline steps that put outside input straight into a shell command. The two uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 5,784 lines, about €8,000 to rebuild.
If Production Readiness rose from 29 to 70, the lowest score rated Strong, the score would rise from 43 to about 56.
Fixed since the last survey: 13 findings
- Cognitive Complexity · ProcessChangelog.print_changelog (cognitive 28) scripts/release_notes.py
- Cognitive Complexity · ProcessChangelog.get_merged_prs (cognitive 25) scripts/release_notes.py
- Secret Scanning · Leaked secret: private-key etc/localhost.key
- Secrets (history) · Secret: private-key etc/localhost.key
- Test Coverage · No test reaches this file src/typescript/clientunarycallimpl.ts
- Test Coverage · No test reaches this file src/typescript/requestinternal.ts
- Test Coverage · No test reaches this file src/typescript/rpcerror.ts
- Test Coverage · No test reaches this file packages/grpc-web/exports.js
- Test Coverage · No test reaches this file src/typescript/unaryresponseinternal.ts
- Test Coverage · No test reaches this file src/typescript/authutil.ts
- Test Coverage · No test reaches this file javascript/net/grpc/web/methodtype.js
- Test Coverage · No test reaches this file javascript/net/grpc/web/metadata.js
- Test Coverage · No test reaches this file src/typescript/methodtype.ts
Rebuild cost: about €8,000 · Estimate
| Cost to rebuild | €2,700 to €13,000, for 44 to 140 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 43. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,784 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 javascript.net.grpc.web | 2 javascript.net.grpc.web.abstractclientbase | 3 javascript.net.grpc.web.calloptions | 4 javascript.net.grpc.web.clientoptions | 5 javascript.net.grpc.web.clientunarycallimpl | 6 javascript.net.grpc.web.grpcwebclientbase | 7 javascript.net.grpc.web.grpcwebclientbase_test | 8 javascript.net.grpc.web.grpcwebclientreadablestream | 9 javascript.net.grpc.web.grpcwebstreamparser | 10 javascript.net.grpc.web.methoddescriptor | 11 javascript.net.grpc.web.request | 12 javascript.net.grpc.web.requestinternal | 13 javascript.net.grpc.web.rpcerror | 14 javascript.net.grpc.web.unaryresponse | 15 javascript.net.grpc.web.unaryresponseinternal | 16 packages.grpc-web | 17 packages.grpc-web.scripts | 18 scripts | 19 scripts.release_notes | 20 src.typescript.clientoptions | 21 src.typescript.clientreadablestream | 22 src.typescript.generictransportinterface | 23 src.typescript.metadata | 24 src.typescript.status | 25 src.typescript.statuscode | 26 src.typescript.abstractclientbase | 27 src.typescript.clientunarycallimpl | 28 src.typescript.grpcwebclientreadablestream | 29 src.typescript.interceptor | 30 src.typescript.methoddescriptorinterface | 31 src.typescript.requestinternal | 32 src.typescript.rpcerror | 33 src.typescript.streambodyclientreadablestream | 34 src.typescript.unaryresponse | 35 src.typescript.unaryresponseinternal | 36 src.typescript.grpcwebclientbase | 37 src.typescript.grpcwebclientbase_test | 38 src.typescript.methoddescriptor | 39 src.typescript.request | 40 src.typescript |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 javascript.net.grpc.web | ||||||||||||||||||||||||||||||||||||||||
| 2 javascript.net.grpc.web.abstractclientbase | ||||||||||||||||||||||||||||||||||||||||
| 3 javascript.net.grpc.web.calloptions | ||||||||||||||||||||||||||||||||||||||||
| 4 javascript.net.grpc.web.clientoptions | ||||||||||||||||||||||||||||||||||||||||
| 5 javascript.net.grpc.web.clientunarycallimpl | ||||||||||||||||||||||||||||||||||||||||
| 6 javascript.net.grpc.web.grpcwebclientbase | ||||||||||||||||||||||||||||||||||||||||
| 7 javascript.net.grpc.web.grpcwebclientbase_test | ||||||||||||||||||||||||||||||||||||||||
| 8 javascript.net.grpc.web.grpcwebclientreadablestream | ||||||||||||||||||||||||||||||||||||||||
| 9 javascript.net.grpc.web.grpcwebstreamparser | ||||||||||||||||||||||||||||||||||||||||
| 10 javascript.net.grpc.web.methoddescriptor | ||||||||||||||||||||||||||||||||||||||||
| 11 javascript.net.grpc.web.request | ||||||||||||||||||||||||||||||||||||||||
| 12 javascript.net.grpc.web.requestinternal | ||||||||||||||||||||||||||||||||||||||||
| 13 javascript.net.grpc.web.rpcerror | ||||||||||||||||||||||||||||||||||||||||
| 14 javascript.net.grpc.web.unaryresponse | ||||||||||||||||||||||||||||||||||||||||
| 15 javascript.net.grpc.web.unaryresponseinternal | ||||||||||||||||||||||||||||||||||||||||
| 16 packages.grpc-web | ||||||||||||||||||||||||||||||||||||||||
| 17 packages.grpc-web.scripts | ||||||||||||||||||||||||||||||||||||||||
| 18 scripts | ||||||||||||||||||||||||||||||||||||||||
| 19 scripts.release_notes | ||||||||||||||||||||||||||||||||||||||||
| 20 src.typescript.clientoptions | ||||||||||||||||||||||||||||||||||||||||
| 21 src.typescript.clientreadablestream | ||||||||||||||||||||||||||||||||||||||||
| 22 src.typescript.generictransportinterface | ||||||||||||||||||||||||||||||||||||||||
| 23 src.typescript.metadata | ||||||||||||||||||||||||||||||||||||||||
| 24 src.typescript.status | ||||||||||||||||||||||||||||||||||||||||
| 25 src.typescript.statuscode | ||||||||||||||||||||||||||||||||||||||||
| 26 src.typescript.abstractclientbase | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 src.typescript.clientunarycallimpl | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 src.typescript.grpcwebclientreadablestream | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 src.typescript.interceptor | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 src.typescript.methoddescriptorinterface | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 src.typescript.requestinternal | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 32 src.typescript.rpcerror | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 src.typescript.streambodyclientreadablestream | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 34 src.typescript.unaryresponse | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 src.typescript.unaryresponseinternal | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 src.typescript.grpcwebclientbase | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 src.typescript.grpcwebclientbase_test | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 src.typescript.methoddescriptor | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 src.typescript.request | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 src.typescript | 1 | 2 | 1 | 1 | 1 | 1 |
26→10 src.typescript.abstractclientbase uses javascript.net.grpc.web.methoddescriptor✕
- Connections
- 1 pair of types, where a type in src.typescript.abstractclientbase uses a type in javascript.net.grpc.web.methoddescriptor.
- The types involved
src.typescript.abstractclientbase.AbstractClientBase→javascript.net.grpc.web.methoddescriptor.MethodDescriptor
- Direction
- src.typescript.abstractclientbase uses javascript.net.grpc.web.methoddescriptor, so a change to javascript.net.grpc.web.methoddescriptor can break src.typescript.abstractclientbase, while a change to src.typescript.abstractclientbase can't break javascript.net.grpc.web.methoddescriptor.
- Position
- Below the diagonal: src.typescript.abstractclientbase uses a module listed above it, which is the healthy direction.
26→21 src.typescript.abstractclientbase uses src.typescript.clientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript.abstractclientbase uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.abstractclientbase.AbstractClientBase→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.abstractclientbase uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.abstractclientbase, while a change to src.typescript.abstractclientbase can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.abstractclientbase uses a module listed above it, which is the healthy direction.
27→21 src.typescript.clientunarycallimpl uses src.typescript.clientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript.clientunarycallimpl uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.clientunarycallimpl.ClientUnaryCallImpl→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.clientunarycallimpl uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.clientunarycallimpl, while a change to src.typescript.clientunarycallimpl can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.clientunarycallimpl uses a module listed above it, which is the healthy direction.
28→13 src.typescript.grpcwebclientreadablestream uses javascript.net.grpc.web.rpcerror✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientreadablestream uses a type in javascript.net.grpc.web.rpcerror.
- The types involved
src.typescript.grpcwebclientreadablestream.GrpcWebClientReadableStream→javascript.net.grpc.web.rpcerror.RpcError
- Direction
- src.typescript.grpcwebclientreadablestream uses javascript.net.grpc.web.rpcerror, so a change to javascript.net.grpc.web.rpcerror can break src.typescript.grpcwebclientreadablestream, while a change to src.typescript.grpcwebclientreadablestream can't break javascript.net.grpc.web.rpcerror.
- Position
- Below the diagonal: src.typescript.grpcwebclientreadablestream uses a module listed above it, which is the healthy direction.
28→21 src.typescript.grpcwebclientreadablestream uses src.typescript.clientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientreadablestream uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.grpcwebclientreadablestream.GrpcWebClientReadableStream→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.grpcwebclientreadablestream uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.grpcwebclientreadablestream, while a change to src.typescript.grpcwebclientreadablestream can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.grpcwebclientreadablestream uses a module listed above it, which is the healthy direction.
28→22 src.typescript.grpcwebclientreadablestream uses src.typescript.generictransportinterface✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientreadablestream uses a type in src.typescript.generictransportinterface.
- The types involved
src.typescript.grpcwebclientreadablestream.GrpcWebClientReadableStream→src.typescript.generictransportinterface.GenericTransportInterface
- Direction
- src.typescript.grpcwebclientreadablestream uses src.typescript.generictransportinterface, so a change to src.typescript.generictransportinterface can break src.typescript.grpcwebclientreadablestream, while a change to src.typescript.grpcwebclientreadablestream can't break src.typescript.generictransportinterface.
- Position
- Below the diagonal: src.typescript.grpcwebclientreadablestream uses a module listed above it, which is the healthy direction.
28→23 src.typescript.grpcwebclientreadablestream uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientreadablestream uses a type in src.typescript.metadata.
- The types involved
src.typescript.grpcwebclientreadablestream.GrpcWebClientReadableStream→src.typescript.metadata.Metadata
- Direction
- src.typescript.grpcwebclientreadablestream uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.grpcwebclientreadablestream, while a change to src.typescript.grpcwebclientreadablestream can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.grpcwebclientreadablestream uses a module listed above it, which is the healthy direction.
28→24 src.typescript.grpcwebclientreadablestream uses src.typescript.status✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientreadablestream uses a type in src.typescript.status.
- The types involved
src.typescript.grpcwebclientreadablestream.GrpcWebClientReadableStream→src.typescript.status.Status
- Direction
- src.typescript.grpcwebclientreadablestream uses src.typescript.status, so a change to src.typescript.status can break src.typescript.grpcwebclientreadablestream, while a change to src.typescript.grpcwebclientreadablestream can't break src.typescript.status.
- Position
- Below the diagonal: src.typescript.grpcwebclientreadablestream uses a module listed above it, which is the healthy direction.
29→11 src.typescript.interceptor uses javascript.net.grpc.web.request✕
- Connections
- 2 pairs of types, where a type in src.typescript.interceptor uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.interceptor.StreamInterceptor→javascript.net.grpc.web.request.Requestsrc.typescript.interceptor.UnaryInterceptor→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.interceptor uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.interceptor, while a change to src.typescript.interceptor can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.interceptor uses a module listed above it, which is the healthy direction.
29→14 src.typescript.interceptor uses javascript.net.grpc.web.unaryresponse✕
- Connections
- 1 pair of types, where a type in src.typescript.interceptor uses a type in javascript.net.grpc.web.unaryresponse.
- The types involved
src.typescript.interceptor.UnaryInterceptor→javascript.net.grpc.web.unaryresponse.UnaryResponse
- Direction
- src.typescript.interceptor uses javascript.net.grpc.web.unaryresponse, so a change to javascript.net.grpc.web.unaryresponse can break src.typescript.interceptor, while a change to src.typescript.interceptor can't break javascript.net.grpc.web.unaryresponse.
- Position
- Below the diagonal: src.typescript.interceptor uses a module listed above it, which is the healthy direction.
29→21 src.typescript.interceptor uses src.typescript.clientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript.interceptor uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.interceptor.StreamInterceptor→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.interceptor uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.interceptor, while a change to src.typescript.interceptor can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.interceptor uses a module listed above it, which is the healthy direction.
30→11 src.typescript.methoddescriptorinterface uses javascript.net.grpc.web.request✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptorinterface uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.methoddescriptorinterface.MethodDescriptorInterface→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.methoddescriptorinterface uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.methoddescriptorinterface, while a change to src.typescript.methoddescriptorinterface can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.methoddescriptorinterface uses a module listed above it, which is the healthy direction.
30→14 src.typescript.methoddescriptorinterface uses javascript.net.grpc.web.unaryresponse✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptorinterface uses a type in javascript.net.grpc.web.unaryresponse.
- The types involved
src.typescript.methoddescriptorinterface.MethodDescriptorInterface→javascript.net.grpc.web.unaryresponse.UnaryResponse
- Direction
- src.typescript.methoddescriptorinterface uses javascript.net.grpc.web.unaryresponse, so a change to javascript.net.grpc.web.unaryresponse can break src.typescript.methoddescriptorinterface, while a change to src.typescript.methoddescriptorinterface can't break javascript.net.grpc.web.unaryresponse.
- Position
- Below the diagonal: src.typescript.methoddescriptorinterface uses a module listed above it, which is the healthy direction.
30→23 src.typescript.methoddescriptorinterface uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptorinterface uses a type in src.typescript.metadata.
- The types involved
src.typescript.methoddescriptorinterface.MethodDescriptorInterface→src.typescript.metadata.Metadata
- Direction
- src.typescript.methoddescriptorinterface uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.methoddescriptorinterface, while a change to src.typescript.methoddescriptorinterface can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.methoddescriptorinterface uses a module listed above it, which is the healthy direction.
31→10 src.typescript.requestinternal uses javascript.net.grpc.web.methoddescriptor✕
- Connections
- 1 pair of types, where a type in src.typescript.requestinternal uses a type in javascript.net.grpc.web.methoddescriptor.
- The types involved
src.typescript.requestinternal.RequestInternal→javascript.net.grpc.web.methoddescriptor.MethodDescriptor
- Direction
- src.typescript.requestinternal uses javascript.net.grpc.web.methoddescriptor, so a change to javascript.net.grpc.web.methoddescriptor can break src.typescript.requestinternal, while a change to src.typescript.requestinternal can't break javascript.net.grpc.web.methoddescriptor.
- Position
- Below the diagonal: src.typescript.requestinternal uses a module listed above it, which is the healthy direction.
31→11 src.typescript.requestinternal uses javascript.net.grpc.web.request✕
- Connections
- 1 pair of types, where a type in src.typescript.requestinternal uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.requestinternal.RequestInternal→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.requestinternal uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.requestinternal, while a change to src.typescript.requestinternal can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.requestinternal uses a module listed above it, which is the healthy direction.
31→23 src.typescript.requestinternal uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.requestinternal uses a type in src.typescript.metadata.
- The types involved
src.typescript.requestinternal.RequestInternal→src.typescript.metadata.Metadata
- Direction
- src.typescript.requestinternal uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.requestinternal, while a change to src.typescript.requestinternal can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.requestinternal uses a module listed above it, which is the healthy direction.
32→23 src.typescript.rpcerror uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.rpcerror uses a type in src.typescript.metadata.
- The types involved
src.typescript.rpcerror.RpcError→src.typescript.metadata.Metadata
- Direction
- src.typescript.rpcerror uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.rpcerror, while a change to src.typescript.rpcerror can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.rpcerror uses a module listed above it, which is the healthy direction.
32→25 src.typescript.rpcerror uses src.typescript.statuscode✕
- Connections
- 1 pair of types, where a type in src.typescript.rpcerror uses a type in src.typescript.statuscode.
- The types involved
src.typescript.rpcerror.RpcError→src.typescript.statuscode.StatusCode
- Direction
- src.typescript.rpcerror uses src.typescript.statuscode, so a change to src.typescript.statuscode can break src.typescript.rpcerror, while a change to src.typescript.rpcerror can't break src.typescript.statuscode.
- Position
- Below the diagonal: src.typescript.rpcerror uses a module listed above it, which is the healthy direction.
33→13 src.typescript.streambodyclientreadablestream uses javascript.net.grpc.web.rpcerror✕
- Connections
- 1 pair of types, where a type in src.typescript.streambodyclientreadablestream uses a type in javascript.net.grpc.web.rpcerror.
- The types involved
src.typescript.streambodyclientreadablestream.StreamBodyClientReadableStream→javascript.net.grpc.web.rpcerror.RpcError
- Direction
- src.typescript.streambodyclientreadablestream uses javascript.net.grpc.web.rpcerror, so a change to javascript.net.grpc.web.rpcerror can break src.typescript.streambodyclientreadablestream, while a change to src.typescript.streambodyclientreadablestream can't break javascript.net.grpc.web.rpcerror.
- Position
- Below the diagonal: src.typescript.streambodyclientreadablestream uses a module listed above it, which is the healthy direction.
33→21 src.typescript.streambodyclientreadablestream uses src.typescript.clientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript.streambodyclientreadablestream uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.streambodyclientreadablestream.StreamBodyClientReadableStream→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.streambodyclientreadablestream uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.streambodyclientreadablestream, while a change to src.typescript.streambodyclientreadablestream can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.streambodyclientreadablestream uses a module listed above it, which is the healthy direction.
33→22 src.typescript.streambodyclientreadablestream uses src.typescript.generictransportinterface✕
- Connections
- 1 pair of types, where a type in src.typescript.streambodyclientreadablestream uses a type in src.typescript.generictransportinterface.
- The types involved
src.typescript.streambodyclientreadablestream.StreamBodyClientReadableStream→src.typescript.generictransportinterface.GenericTransportInterface
- Direction
- src.typescript.streambodyclientreadablestream uses src.typescript.generictransportinterface, so a change to src.typescript.generictransportinterface can break src.typescript.streambodyclientreadablestream, while a change to src.typescript.streambodyclientreadablestream can't break src.typescript.generictransportinterface.
- Position
- Below the diagonal: src.typescript.streambodyclientreadablestream uses a module listed above it, which is the healthy direction.
33→23 src.typescript.streambodyclientreadablestream uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.streambodyclientreadablestream uses a type in src.typescript.metadata.
- The types involved
src.typescript.streambodyclientreadablestream.StreamBodyClientReadableStream→src.typescript.metadata.Metadata
- Direction
- src.typescript.streambodyclientreadablestream uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.streambodyclientreadablestream, while a change to src.typescript.streambodyclientreadablestream can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.streambodyclientreadablestream uses a module listed above it, which is the healthy direction.
33→24 src.typescript.streambodyclientreadablestream uses src.typescript.status✕
- Connections
- 1 pair of types, where a type in src.typescript.streambodyclientreadablestream uses a type in src.typescript.status.
- The types involved
src.typescript.streambodyclientreadablestream.StreamBodyClientReadableStream→src.typescript.status.Status
- Direction
- src.typescript.streambodyclientreadablestream uses src.typescript.status, so a change to src.typescript.status can break src.typescript.streambodyclientreadablestream, while a change to src.typescript.streambodyclientreadablestream can't break src.typescript.status.
- Position
- Below the diagonal: src.typescript.streambodyclientreadablestream uses a module listed above it, which is the healthy direction.
34→23 src.typescript.unaryresponse uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.unaryresponse uses a type in src.typescript.metadata.
- The types involved
src.typescript.unaryresponse.UnaryResponse→src.typescript.metadata.Metadata
- Direction
- src.typescript.unaryresponse uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.unaryresponse, while a change to src.typescript.unaryresponse can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.unaryresponse uses a module listed above it, which is the healthy direction.
35→14 src.typescript.unaryresponseinternal uses javascript.net.grpc.web.unaryresponse✕
- Connections
- 1 pair of types, where a type in src.typescript.unaryresponseinternal uses a type in javascript.net.grpc.web.unaryresponse.
- The types involved
src.typescript.unaryresponseinternal.UnaryResponseInternal→javascript.net.grpc.web.unaryresponse.UnaryResponse
- Direction
- src.typescript.unaryresponseinternal uses javascript.net.grpc.web.unaryresponse, so a change to javascript.net.grpc.web.unaryresponse can break src.typescript.unaryresponseinternal, while a change to src.typescript.unaryresponseinternal can't break javascript.net.grpc.web.unaryresponse.
- Position
- Below the diagonal: src.typescript.unaryresponseinternal uses a module listed above it, which is the healthy direction.
35→23 src.typescript.unaryresponseinternal uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.unaryresponseinternal uses a type in src.typescript.metadata.
- The types involved
src.typescript.unaryresponseinternal.UnaryResponseInternal→src.typescript.metadata.Metadata
- Direction
- src.typescript.unaryresponseinternal uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.unaryresponseinternal, while a change to src.typescript.unaryresponseinternal can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.unaryresponseinternal uses a module listed above it, which is the healthy direction.
36→2 src.typescript.grpcwebclientbase uses javascript.net.grpc.web.abstractclientbase✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase uses a type in javascript.net.grpc.web.abstractclientbase.
- The types involved
src.typescript.grpcwebclientbase.GrpcWebClientBase→javascript.net.grpc.web.abstractclientbase.AbstractClientBase
- Direction
- src.typescript.grpcwebclientbase uses javascript.net.grpc.web.abstractclientbase, so a change to javascript.net.grpc.web.abstractclientbase can break src.typescript.grpcwebclientbase, while a change to src.typescript.grpcwebclientbase can't break javascript.net.grpc.web.abstractclientbase.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase uses a module listed above it, which is the healthy direction.
36→4 src.typescript.grpcwebclientbase uses javascript.net.grpc.web.clientoptions✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase uses a type in javascript.net.grpc.web.clientoptions.
- The types involved
src.typescript.grpcwebclientbase.GrpcWebClientBase→javascript.net.grpc.web.clientoptions.ClientOptions
- Direction
- src.typescript.grpcwebclientbase uses javascript.net.grpc.web.clientoptions, so a change to javascript.net.grpc.web.clientoptions can break src.typescript.grpcwebclientbase, while a change to src.typescript.grpcwebclientbase can't break javascript.net.grpc.web.clientoptions.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase uses a module listed above it, which is the healthy direction.
36→10 src.typescript.grpcwebclientbase uses javascript.net.grpc.web.methoddescriptor✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase uses a type in javascript.net.grpc.web.methoddescriptor.
- The types involved
src.typescript.grpcwebclientbase.GrpcWebClientBase→javascript.net.grpc.web.methoddescriptor.MethodDescriptor
- Direction
- src.typescript.grpcwebclientbase uses javascript.net.grpc.web.methoddescriptor, so a change to javascript.net.grpc.web.methoddescriptor can break src.typescript.grpcwebclientbase, while a change to src.typescript.grpcwebclientbase can't break javascript.net.grpc.web.methoddescriptor.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase uses a module listed above it, which is the healthy direction.
36→11 src.typescript.grpcwebclientbase uses javascript.net.grpc.web.request✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.grpcwebclientbase.GrpcWebClientBase→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.grpcwebclientbase uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.grpcwebclientbase, while a change to src.typescript.grpcwebclientbase can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase uses a module listed above it, which is the healthy direction.
36→21 src.typescript.grpcwebclientbase uses src.typescript.clientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.grpcwebclientbase.GrpcWebClientBase→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.grpcwebclientbase uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.grpcwebclientbase, while a change to src.typescript.grpcwebclientbase can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase uses a module listed above it, which is the healthy direction.
36→26 src.typescript.grpcwebclientbase uses src.typescript.abstractclientbase✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase uses a type in src.typescript.abstractclientbase.
- The types involved
src.typescript.grpcwebclientbase.GrpcWebClientBase→src.typescript.abstractclientbase.PromiseCallOptions
- Direction
- src.typescript.grpcwebclientbase uses src.typescript.abstractclientbase, so a change to src.typescript.abstractclientbase can break src.typescript.grpcwebclientbase, while a change to src.typescript.grpcwebclientbase can't break src.typescript.abstractclientbase.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase uses a module listed above it, which is the healthy direction.
37→11 src.typescript.grpcwebclientbase_test uses javascript.net.grpc.web.request✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase_test uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.grpcwebclientbase_test.StreamResponseInterceptor→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.grpcwebclientbase_test uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.grpcwebclientbase_test, while a change to src.typescript.grpcwebclientbase_test can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase_test uses a module listed above it, which is the healthy direction.
37→21 src.typescript.grpcwebclientbase_test uses src.typescript.clientreadablestream✕
- Connections
- 2 pairs of types, where a type in src.typescript.grpcwebclientbase_test uses a type in src.typescript.clientreadablestream.
- The types involved
src.typescript.grpcwebclientbase_test.InterceptedStream→src.typescript.clientreadablestream.ClientReadableStreamsrc.typescript.grpcwebclientbase_test.StreamResponseInterceptor→src.typescript.clientreadablestream.ClientReadableStream
- Direction
- src.typescript.grpcwebclientbase_test uses src.typescript.clientreadablestream, so a change to src.typescript.clientreadablestream can break src.typescript.grpcwebclientbase_test, while a change to src.typescript.grpcwebclientbase_test can't break src.typescript.clientreadablestream.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase_test uses a module listed above it, which is the healthy direction.
37→29 src.typescript.grpcwebclientbase_test uses src.typescript.interceptor✕
- Connections
- 1 pair of types, where a type in src.typescript.grpcwebclientbase_test uses a type in src.typescript.interceptor.
- The types involved
src.typescript.grpcwebclientbase_test.StreamResponseInterceptor→src.typescript.interceptor.StreamInterceptor
- Direction
- src.typescript.grpcwebclientbase_test uses src.typescript.interceptor, so a change to src.typescript.interceptor can break src.typescript.grpcwebclientbase_test, while a change to src.typescript.grpcwebclientbase_test can't break src.typescript.interceptor.
- Position
- Below the diagonal: src.typescript.grpcwebclientbase_test uses a module listed above it, which is the healthy direction.
38→11 src.typescript.methoddescriptor uses javascript.net.grpc.web.request✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptor uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.methoddescriptor.MethodDescriptor→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.methoddescriptor uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.methoddescriptor, while a change to src.typescript.methoddescriptor can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.methoddescriptor uses a module listed above it, which is the healthy direction.
38→14 src.typescript.methoddescriptor uses javascript.net.grpc.web.unaryresponse✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptor uses a type in javascript.net.grpc.web.unaryresponse.
- The types involved
src.typescript.methoddescriptor.MethodDescriptor→javascript.net.grpc.web.unaryresponse.UnaryResponse
- Direction
- src.typescript.methoddescriptor uses javascript.net.grpc.web.unaryresponse, so a change to javascript.net.grpc.web.unaryresponse can break src.typescript.methoddescriptor, while a change to src.typescript.methoddescriptor can't break javascript.net.grpc.web.unaryresponse.
- Position
- Below the diagonal: src.typescript.methoddescriptor uses a module listed above it, which is the healthy direction.
38→23 src.typescript.methoddescriptor uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptor uses a type in src.typescript.metadata.
- The types involved
src.typescript.methoddescriptor.MethodDescriptor→src.typescript.metadata.Metadata
- Direction
- src.typescript.methoddescriptor uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.methoddescriptor, while a change to src.typescript.methoddescriptor can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.methoddescriptor uses a module listed above it, which is the healthy direction.
38→30 src.typescript.methoddescriptor uses src.typescript.methoddescriptorinterface✕
- Connections
- 1 pair of types, where a type in src.typescript.methoddescriptor uses a type in src.typescript.methoddescriptorinterface.
- The types involved
src.typescript.methoddescriptor.MethodDescriptor→src.typescript.methoddescriptorinterface.MethodDescriptorInterface
- Direction
- src.typescript.methoddescriptor uses src.typescript.methoddescriptorinterface, so a change to src.typescript.methoddescriptorinterface can break src.typescript.methoddescriptor, while a change to src.typescript.methoddescriptor can't break src.typescript.methoddescriptorinterface.
- Position
- Below the diagonal: src.typescript.methoddescriptor uses a module listed above it, which is the healthy direction.
39→11 src.typescript.request uses javascript.net.grpc.web.request✕
- Connections
- 1 pair of types, where a type in src.typescript.request uses a type in javascript.net.grpc.web.request.
- The types involved
src.typescript.request.Request→javascript.net.grpc.web.request.Request
- Direction
- src.typescript.request uses javascript.net.grpc.web.request, so a change to javascript.net.grpc.web.request can break src.typescript.request, while a change to src.typescript.request can't break javascript.net.grpc.web.request.
- Position
- Below the diagonal: src.typescript.request uses a module listed above it, which is the healthy direction.
39→23 src.typescript.request uses src.typescript.metadata✕
- Connections
- 1 pair of types, where a type in src.typescript.request uses a type in src.typescript.metadata.
- The types involved
src.typescript.request.Request→src.typescript.metadata.Metadata
- Direction
- src.typescript.request uses src.typescript.metadata, so a change to src.typescript.metadata can break src.typescript.request, while a change to src.typescript.request can't break src.typescript.metadata.
- Position
- Below the diagonal: src.typescript.request uses a module listed above it, which is the healthy direction.
39→30 src.typescript.request uses src.typescript.methoddescriptorinterface✕
- Connections
- 1 pair of types, where a type in src.typescript.request uses a type in src.typescript.methoddescriptorinterface.
- The types involved
src.typescript.request.Request→src.typescript.methoddescriptorinterface.MethodDescriptorInterface
- Direction
- src.typescript.request uses src.typescript.methoddescriptorinterface, so a change to src.typescript.methoddescriptorinterface can break src.typescript.request, while a change to src.typescript.request can't break src.typescript.methoddescriptorinterface.
- Position
- Below the diagonal: src.typescript.request uses a module listed above it, which is the healthy direction.
40→7 src.typescript uses javascript.net.grpc.web.grpcwebclientbase_test✕
- Connections
- 1 pair of types, where a type in src.typescript uses a type in javascript.net.grpc.web.grpcwebclientbase_test.
- The types involved
src.typescript.grpcwebclientbase_test→javascript.net.grpc.web.grpcwebclientbase_test.MockRequest
- Direction
- src.typescript uses javascript.net.grpc.web.grpcwebclientbase_test, so a change to javascript.net.grpc.web.grpcwebclientbase_test can break src.typescript, while a change to src.typescript can't break javascript.net.grpc.web.grpcwebclientbase_test.
- Position
- Below the diagonal: src.typescript uses a module listed above it, which is the healthy direction.
40→10 src.typescript uses javascript.net.grpc.web.methoddescriptor✕
- Connections
- 2 pairs of types, where a type in src.typescript uses a type in javascript.net.grpc.web.methoddescriptor.
- The types involved
src.typescript.abstractclientbase→javascript.net.grpc.web.methoddescriptor.MethodDescriptorsrc.typescript.grpcwebclientbase_test→javascript.net.grpc.web.methoddescriptor.MethodDescriptor
- Direction
- src.typescript uses javascript.net.grpc.web.methoddescriptor, so a change to javascript.net.grpc.web.methoddescriptor can break src.typescript, while a change to src.typescript can't break javascript.net.grpc.web.methoddescriptor.
- Position
- Below the diagonal: src.typescript uses a module listed above it, which is the healthy direction.
40→13 src.typescript uses javascript.net.grpc.web.rpcerror✕
- Connections
- 1 pair of types, where a type in src.typescript uses a type in javascript.net.grpc.web.rpcerror.
- The types involved
src.typescript.streambodyclientreadablestream→javascript.net.grpc.web.rpcerror.RpcError
- Direction
- src.typescript uses javascript.net.grpc.web.rpcerror, so a change to javascript.net.grpc.web.rpcerror can break src.typescript, while a change to src.typescript can't break javascript.net.grpc.web.rpcerror.
- Position
- Below the diagonal: src.typescript uses a module listed above it, which is the healthy direction.
40→25 src.typescript uses src.typescript.statuscode✕
- Connections
- 1 pair of types, where a type in src.typescript uses a type in src.typescript.statuscode.
- The types involved
src.typescript.statuscode→src.typescript.statuscode.StatusCode
- Direction
- src.typescript uses src.typescript.statuscode, so a change to src.typescript.statuscode can break src.typescript, while a change to src.typescript can't break src.typescript.statuscode.
- Position
- Below the diagonal: src.typescript uses a module listed above it, which is the healthy direction.
40→33 src.typescript uses src.typescript.streambodyclientreadablestream✕
- Connections
- 1 pair of types, where a type in src.typescript uses a type in src.typescript.streambodyclientreadablestream.
- The types involved
src.typescript.streambodyclientreadablestream→src.typescript.streambodyclientreadablestream.AsyncStack
- Direction
- src.typescript uses src.typescript.streambodyclientreadablestream, so a change to src.typescript.streambodyclientreadablestream can break src.typescript, while a change to src.typescript can't break src.typescript.streambodyclientreadablestream.
- Position
- Below the diagonal: src.typescript uses a module listed above it, which is the healthy direction.
40→37 src.typescript uses src.typescript.grpcwebclientbase_test✕
- Connections
- 1 pair of types, where a type in src.typescript uses a type in src.typescript.grpcwebclientbase_test.
- The types involved
src.typescript.grpcwebclientbase_test→src.typescript.grpcwebclientbase_test.AllowedResponseType
- Direction
- src.typescript uses src.typescript.grpcwebclientbase_test, so a change to src.typescript.grpcwebclientbase_test can break src.typescript, while a change to src.typescript can't break src.typescript.grpcwebclientbase_test.
- Position
- Below the diagonal: src.typescript uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A02:2025 — Security Misconfiguration | 54 | High / Critical |
| A05:2025 — Injection | 17 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | High / Critical |
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt pino (or winston) and log at meaningful points in the services you run. | +5.5 pts | Medium | Observability |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +5.5 pts | Medium | Security & performance tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +5.3 pts | Medium | Test Coverage |
| 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. | +2.5 pts | Medium | Code Duplication |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| 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 `?`). | +1.7 pts | Medium | Nullable reference types |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +0.9 pts | Low | Static Analysis (SAST) |
| Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with release_notes.py, statuscode.js, abstractclientbase.js. | +0.9 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.9 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/typescript/streambodyclientreadablestream.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/typescript/grpcwebclientbase_test.ts | 6.9 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 52 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 52 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, 202 of 218 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
- D4 Code Duplication — 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. Most of this repository's production source (.cc) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load. Duplication in .ts is measured by R10 Code Duplication and is not part of this gap.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for packages/grpc-web/ failed in the analyzer sandbox (npm error code 127), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the mocha suite in packages/grpc-web/ was NOT MEASURED: the dependency install for packages/grpc-web/ failed in the analyzer sandbox (npm error code 127), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 10 production npm declaration(s) across 8 REDACTED (2 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, and no committed lockfile here resolves to the concrete versions that question is asked about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's committed lockfile was read and it resolves no production dependency: everything it installs is declared under `devDependencies`, or is a workspace-internal package with no registry release behind it. Licences are resolved from registry.npmjs.org, because an npm checkout does not contain its dependencies' licences. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- 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 (packages/grpc-web/package.json), 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 229 sampled here came from .js/.ts files. This repository's .cc source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — 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.
- 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 DockerCompose (docker-compose.yml). compose up failed (exit 17 — an image could not be built) — interop-client Warning pull access denied for grpcweb/interop-client, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: process "/bin/sh -c bazel build net/grpc/gateway/examples/echo:server" did not complete successfully: exit code: 36; runtime evidence skipped.
- 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.
- 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.
- P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
- 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.
- X12 Unreachable branch — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X21 Side-effecting pattern guard — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X3 Exception handling — 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.
- 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GrpcWebClientReadableStream.constructor at 34. A further 4 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being statuscode.StatusCode.statusCodeName at 18 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: javascript/net/grpc/web/statuscode.js (statusCodeName at 18), javascript/net/grpc/web/statuscode.js (statuscode.StatusCode.statusCodeName at 18), src/typescript/statuscode.ts (statuscode.getHttpStatus at 18). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with GrpcWebClientReadableStream.constructor (cyclomatic 34), GrpcWebClientReadableStream.constructor (cyclomatic 34), GrpcWebStreamParser.parse (cyclomatic 19). — 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 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was GrpcWebClientReadableStream.constructor at 72.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with GrpcWebClientReadableStream.constructor (cognitive 72), GrpcWebClientReadableStream.constructor (cognitive 70), parse (cognitive 22). — 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 4 together lifts Cognitive Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 MethodTooLong finding(s) in God Classes — start with grpcwebclientreadablestream.js, grpcwebclientreadablestream.ts. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
3 production modules (npm+Bazel), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is javascript/net/grpc/web/grpcwebclientreadablestream.js. Counted over 15 of the 55 production source files in this repository: 39 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
D17 · Explicit Debt
7 deducted task-comment markers across 2805 LoC (0.1/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 7 TodoComment finding(s) in Explicit Debt — start with grpcwebclientbase_test.ts (3), streambodyclientreadablestream.ts (2), clientreadablestream.ts. — One of this dimension's main actionable groups (7 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 10 document(s) read across 3 unit(s).
D24 · Comment Value
0 of 86 judged comments only repeat the code they sit on (0.0 %). 5 comment(s) in another language or script were not judged.
D27 · Navigability
31 % of calls cross a namespace and 10 % go through an interface, but 60 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .js/.ts source only — this repository's .cc was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
17 finding(s): 0 critical, 14 high, 3 medium, 0 low. 8 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 2 file(s) — `scripts/run_basic_tests.sh` (line 29), `scripts/run_interop_tests.sh` (line 33) — 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 3 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 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 8 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 (8 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
3 finding(s): 0 critical, 3 high, 0 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
D31 · IaC & Container Security
54 finding(s): 0 critical, 17 high, 22 medium, 15 low.
What to do
- Resolve the 22 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (22). — One of this dimension's main actionable groups (22 warning-level).
- Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (17). — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 15 Low IaC finding(s) in IaC & Container Security — start with REDACTED (15). — One of this dimension's main actionable groups (15 recommendation-level).
D34 · Knowledge Freshness
7 of 16 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scripts/release_notes.py. Counted over 16 of the 55 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with release_notes.py, statuscode.js, abstractclientbase.js. — One of this dimension's main actionable groups (7 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- 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. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- 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
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 53 Python, JavaScript/TypeScript production file(s) this check read across 4 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 4 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
- `net/grpc/gateway/examples/echo/commonjs-example/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`. — net/grpc/gateway/examples/echo/commonjs-example/package.json:6
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
R1 · Type Safety
R10 · Code Duplication
- javascript/net/grpc/web/grpcwebclientbase_test.js:202 · src/typescript/grpcwebclientbase_test.ts:228 — the two spans are one implementation copied and then locally edited — 792 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. — javascript/net/grpc/web/grpcwebclientbase_test.js:202
- javascript/net/grpc/web/statuscode.js:150 · src/typescript/statuscode.ts:124 — the two spans are one implementation copied and then locally edited — 385 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. — javascript/net/grpc/web/statuscode.js:150
- javascript/net/grpc/web/grpcwebclientbase.js:228 · src/typescript/grpcwebclientbase.ts:228 — the two spans are one implementation copied and then locally edited — 631 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. — javascript/net/grpc/web/grpcwebclientbase.js:228
- javascript/net/grpc/web/grpcwebclientreadablestream.js:235 · src/typescript/grpcwebclientreadablestream.ts:214 — the two spans are one implementation copied and then locally edited — 474 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. — javascript/net/grpc/web/grpcwebclientreadablestream.js:235
- src/typescript/grpcwebclientreadablestream.ts:431 · src/typescript/streambodyclientreadablestream.ts:373 — 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. — src/typescript/grpcwebclientreadablestream.ts:431
- src/typescript/grpcwebclientbase_test.ts:172 · src/typescript/grpcwebclientbase_test.ts:201 — 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. — src/typescript/grpcwebclientbase_test.ts:172
- javascript/net/grpc/web/grpcwebclientbase_test.js:152 · javascript/net/grpc/web/grpcwebclientbase_test.js:178 — 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. — javascript/net/grpc/web/grpcwebclientbase_test.js:152
- src/typescript/grpcwebstreamparser_test.ts:43 · src/typescript/grpcwebstreamparser_test.ts:61 — 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. — src/typescript/grpcwebstreamparser_test.ts:43
- src/typescript/grpcwebclientbase_test.ts:126 · src/typescript/grpcwebclientbase_test.ts:151 — 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. — src/typescript/grpcwebclientbase_test.ts:126
- src/typescript/streambodyclientreadablestream.ts:324 · src/typescript/streambodyclientreadablestream.ts:357 — the two spans are one implementation copied and then locally edited — 92 tokens are still identical, in the same order in both spans, 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. — src/typescript/streambodyclientreadablestream.ts:324
- src/typescript/grpcwebclientreadablestream.ts:232 · src/typescript/streambodyclientreadablestream.ts:205 — 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. — src/typescript/grpcwebclientreadablestream.ts:232
- src/typescript/grpcwebclientreadablestream.ts:281 · src/typescript/grpcwebclientreadablestream.ts:327 — 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. — src/typescript/grpcwebclientreadablestream.ts:281
- src/typescript/grpcwebclientbase_test.ts:99 · src/typescript/grpcwebclientbase_test.ts:261 · src/typescript/grpcwebclientbase_test.ts:294 · src/typescript/grpcwebclientbase_test.ts:357 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/typescript/grpcwebclientbase_test.ts:99
- javascript/net/grpc/web/grpcwebclientbase_test.js:62 · javascript/net/grpc/web/grpcwebclientbase_test.js:89 · javascript/net/grpc/web/grpcwebclientbase_test.js:312 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — javascript/net/grpc/web/grpcwebclientbase_test.js:62
- javascript/net/grpc/web/grpcwebstreamparser_test.js:66 · javascript/net/grpc/web/grpcwebstreamparser_test.js:81 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:66
- src/typescript/grpcwebclientbase_test.ts:68 · src/typescript/grpcwebclientbase_test.ts:98 · src/typescript/grpcwebclientbase_test.ts:260 · src/typescript/grpcwebclientbase_test.ts:293 · +1 more site(s) not listed — all 5 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. — src/typescript/grpcwebclientbase_test.ts:68
- src/typescript/grpcwebstreamparser_test.ts:82 · src/typescript/grpcwebstreamparser_test.ts:96 — 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. — src/typescript/grpcwebstreamparser_test.ts:82
- javascript/net/grpc/web/grpcwebclientbase_test.js:111 · javascript/net/grpc/web/grpcwebclientbase_test.js:133 — 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. — javascript/net/grpc/web/grpcwebclientbase_test.js:111
- javascript/net/grpc/web/grpcwebclientreadablestream.js:411 · javascript/net/grpc/web/grpcwebclientreadablestream.js:431 — 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. — javascript/net/grpc/web/grpcwebclientreadablestream.js:411
- src/typescript/grpcwebclientbase.ts:277 · src/typescript/grpcwebclientbase.ts:324 — 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. — src/typescript/grpcwebclientbase.ts:277
- src/typescript/grpcwebclientbase_test.ts:85 · src/typescript/grpcwebclientbase_test.ts:115 · src/typescript/grpcwebclientbase_test.ts:140 · src/typescript/grpcwebclientbase_test.ts:165 — all 4 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. — src/typescript/grpcwebclientbase_test.ts:85
- javascript/net/grpc/web/grpcwebclientbase_test.js:98 · javascript/net/grpc/web/grpcwebclientbase_test.js:142 — 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. — javascript/net/grpc/web/grpcwebclientbase_test.js:98
- javascript/net/grpc/web/grpcwebstreamparser_test.js:56 · javascript/net/grpc/web/grpcwebstreamparser_test.js:103 · javascript/net/grpc/web/grpcwebstreamparser_test.js:139 · javascript/net/grpc/web/grpcwebstreamparser_test.js:221 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — javascript/net/grpc/web/grpcwebstreamparser_test.js:56
- javascript/net/grpc/web/grpcwebstreamparser_test.js:93 · javascript/net/grpc/web/grpcwebstreamparser_test.js:107 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:93
- javascript/net/grpc/web/grpcwebstreamparser_test.js:226 · javascript/net/grpc/web/grpcwebstreamparser_test.js:272 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:226
- javascript/net/grpc/web/grpcwebclientbase_test.js:173 · javascript/net/grpc/web/grpcwebclientbase_test.js:198 — 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. — javascript/net/grpc/web/grpcwebclientbase_test.js:173
- src/typescript/grpcwebclientbase_test.ts:196 · src/typescript/grpcwebclientbase_test.ts:224 — 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. — src/typescript/grpcwebclientbase_test.ts:196
- src/typescript/grpcwebstreamparser_test.ts:109 · src/typescript/grpcwebstreamparser_test.ts:169 — 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. — src/typescript/grpcwebstreamparser_test.ts:109
- javascript/net/grpc/web/grpcwebclientbase.js:26 · javascript/net/grpc/web/grpcwebclientreadablestream.js:29 · javascript/net/grpc/web/methoddescriptor.js:7 · javascript/net/grpc/web/methoddescriptorinterface.js:7 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — javascript/net/grpc/web/grpcwebclientbase.js:26
- javascript/net/grpc/web/grpcwebstreamparser_test.js:116 · javascript/net/grpc/web/grpcwebstreamparser_test.js:220 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:116
- javascript/net/grpc/web/grpcwebstreamparser_test.js:134 · javascript/net/grpc/web/grpcwebstreamparser_test.js:168 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:134
- javascript/net/grpc/web/grpcwebstreamparser_test.js:148 · javascript/net/grpc/web/grpcwebstreamparser_test.js:158 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:148
- javascript/net/grpc/web/grpcwebstreamparser_test.js:205 · javascript/net/grpc/web/grpcwebstreamparser_test.js:213 — 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. — javascript/net/grpc/web/grpcwebstreamparser_test.js:205
- src/typescript/grpcwebstreamparser_test.ts:194 · src/typescript/grpcwebstreamparser_test.ts:200 · src/typescript/grpcwebstreamparser_test.ts:206 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — src/typescript/grpcwebstreamparser_test.ts:194
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
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 53; 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. — javascript/net/grpc/web/grpcwebclientreadablestream.js:140
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 51; 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. — src/typescript/grpcwebclientreadablestream.ts:116
- (anonymous) has cyclomatic complexity 15 and cognitive complexity 18; 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) — javascript/net/grpc/web/grpcwebclientreadablestream.js:227, src/typescript/grpcwebclientreadablestream.ts:206
- constructor 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. — javascript/net/grpc/web/grpcwebclientbase.js:59
- parse has cyclomatic complexity 13 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. — src/typescript/grpcwebstreamparser.ts:118
- parse has cyclomatic complexity 11 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. — javascript/net/grpc/web/grpcwebstreamparser.js:176
R3 · Large Files
- src/typescript/grpcwebclientbase_test.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/typescript/grpcwebclientbase_test.ts:1
- src/typescript/grpcwebclientreadablestream.ts has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/typescript/grpcwebclientreadablestream.ts:1
- src/typescript/grpcwebclientbase.ts has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/typescript/grpcwebclientbase.ts:1
- javascript/net/grpc/web/grpcwebclientreadablestream.js has 416 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — javascript/net/grpc/web/grpcwebclientreadablestream.js: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
- packages/grpc-web/test/tsc-tests/client01.ts:20 imports './generated/test01_pb', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/grpc-web/test/tsc-tests/client01.ts:20
- packages/grpc-web/test/tsc-tests/client02.ts:20 imports './generated/test03_pb', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/grpc-web/test/tsc-tests/client02.ts:20
- packages/grpc-web/test/tsc-tests/client03.ts:20 imports './generated/echo_pb', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/grpc-web/test/tsc-tests/client03.ts:20
- packages/grpc-web/test/tsc-tests/client04.ts:20 imports './generated/echo_pb', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/grpc-web/test/tsc-tests/client04.ts:20
- packages/grpc-web/test/tsc-tests/client05.ts:20 imports './generated/echo_pb', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/grpc-web/test/tsc-tests/client05.ts:20
- packages/grpc-web/test/tsc-tests/client06.ts:20 imports './generated/echo_pb', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/grpc-web/test/tsc-tests/client06.ts:20
- 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. (×34) — src/typescript/grpcwebclientreadablestream.ts:1, src/typescript/grpcwebclientbase_test.ts:1, src/typescript/grpcwebclientbase.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- This repository declares test tooling, and the ✓ above records that declaration — but packages/grpc-web/test/tsc-tests/client01.ts and 5 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/grpc-web/test/tsc-tests/client01.ts:20
What to do
- Add eslint as REDACTED scripts and run them in CI.
R7 · Dead Code
- 49 file(s) (~6596 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.
- Unreachable from the 12 application, 7 tooling and 16 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 (12 application, 7 tooling, 16 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 (×2) — packages/grpc-web/externs.js, packages/closure-wrapper/empty.js
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. (×2) — src/typescript/grpcwebclientbase_test.ts:6, src/typescript/grpcwebclientbase_test.ts:16
- Declared in test/interop/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
- src/typescript/methoddescriptor.ts → src/typescript/requestinternal.ts → src/typescript/methoddescriptor.ts — src/typescript/methoddescriptor.ts:5
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X3 · Exception handling
X5 · Nullable reference types
- 1/3 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.
- ~15.7 `!` null assertions per 1k TypeScript source lines — 39 assertion(s) across the 2490 source line(s) of the 22 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/typescript/streambodyclientreadablestream.ts (23), src/typescript/grpcwebclientreadablestream.ts (11), src/typescript/grpcwebclientbase.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 53% | Adequate — gated by R10, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 78% | Strong | Strongest area. |
| Maturity | 68% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 29% | Weak — gated by R4, P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 50% | Weak — gated by D29, D31, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 4 observation(s) recorded · Not scored — 10 production npm declaration(s) across 8 REDACTED (2 of them the product) were read for PINNING discipline (1 defect(s) reported), but the outdated/deprecated signal needs registry.npmjs.org, and no committed lockfile here resolves to the concrete versions that question is asked about, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- SC1 Supply-chain hygiene — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 73 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript 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.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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 — compose up failed (exit 17 — an image could not be built) — interop-client Warning pull access denied for grpcweb/interop-client, repository does not exist or may require 'docker login': denied: requested access to the resource is denied failed to solve: process "/bin/sh -c bazel build net/grpc/gateway/examples/echo:server" did not complete successfully: exit code: 36; runtime evidence skipped 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 — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~943 lines of test source are present (.ts) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not measured — JavaScript/TypeScript suite did not run
- D14 License Compliance — npm licences not graded — this repository's lockfile resolves no production dependency
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (802 declarations, no unit with a dominant convention).
- 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"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 measured no build unit over this repository's .cc, .ts source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D4 Code Duplication — Duplication not measured — .cc not exposed to the token comparison
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- 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 — packages/grpc-web/ runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. 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 — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 38 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite aborts before any test executes: test/interop/
- REDACTED
- Unlisted import 'jasmine' src/typescript/grpcwebclientbase_test.ts:6
- Unlisted import 'mock-xmlhttprequest' src/typescript/grpcwebclientbase_test.ts:16
- Import cycle (2 files) src/typescript/methoddescriptor.ts:5
Serious — 144 finding(s)
- No test reaches this file src/typescript/grpcwebclientreadablestream.ts:1
- No test reaches this file src/typescript/grpcwebclientbase_test.ts:1
- No test reaches this file src/typescript/grpcwebclientbase.ts:1
- No test reaches this file javascript/net/grpc/web/grpcwebclientreadablestream.js:1
- No test reaches this file javascript/net/grpc/web/grpcwebclientbase_test.js:1
- No test reaches this file src/typescript/streambodyclientreadablestream.ts:1
- No test reaches this file javascript/net/grpc/web/grpcwebstreamparser.js:1
- No test reaches this file javascript/net/grpc/web/grpcwebstreamparser_test.js:1
- No test reaches this file src/typescript/grpcwebstreamparser.ts:1
- No test reaches this file javascript/net/grpc/web/statuscode.js:1
- No test reaches this file src/typescript/statuscode.ts:1
- No test reaches this file src/typescript/grpcwebstreamparser_test.ts:1
- No test reaches this file javascript/net/grpc/web/methoddescriptor.js:1
- No test reaches this file javascript/net/grpc/web/abstractclientbase.js:1
- No test reaches this file packages/grpc-web/protractor_spec.js:1
- No test reaches this file javascript/net/grpc/web/requestinternal.js:1
- No test reaches this file javascript/net/grpc/web/clientreadablestream.js:1
- No test reaches this file javascript/net/grpc/web/interceptor.js:1
- No test reaches this file javascript/net/grpc/web/clientoptions.js:1
- No test reaches this file javascript/net/grpc/web/unaryresponseinternal.js:1
- No test reaches this file javascript/net/grpc/web/calloptions.js:1
- No test reaches this file src/typescript/abstractclientbase.ts:1
- No test reaches this file packages/grpc-web/scripts/build.js:1
- No test reaches this file javascript/net/grpc/web/rpcerror.js:1
- No test reaches this file src/typescript/methoddescriptor.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/typescript/clientreadablestream.ts:22
- TodoComment src/typescript/grpcwebclientbase.ts:80
- TodoComment src/typescript/grpcwebclientbase_test.ts:438
- TodoComment src/typescript/grpcwebclientbase_test.ts:463
- TodoComment src/typescript/grpcwebclientbase_test.ts:470
- TodoComment src/typescript/streambodyclientreadablestream.ts:221
- TodoComment src/typescript/streambodyclientreadablestream.ts:325
- This test file cannot be loaded packages/grpc-web/test/tsc-tests/client01.ts:20
- This test file cannot be loaded packages/grpc-web/test/tsc-tests/client02.ts:20
- This test file cannot be loaded packages/grpc-web/test/tsc-tests/client03.ts:20
- This test file cannot be loaded packages/grpc-web/test/tsc-tests/client04.ts:20
- This test file cannot be loaded packages/grpc-web/test/tsc-tests/client05.ts:20
- This test file cannot be loaded packages/grpc-web/test/tsc-tests/client06.ts:20
- JavaScript dependencies are not locked net/grpc/gateway/examples/echo/commonjs-example/package.json:6
- JavaScript dependencies are not locked net/grpc/gateway/examples/echo/node-server/package.json:5
- JavaScript dependencies are not locked net/grpc/gateway/examples/echo/package.json:7
- JavaScript dependencies are not locked net/grpc/gateway/examples/echo/ts-example/package.json:2
- JavaScript dependencies are not locked net/grpc/gateway/examples/helloworld/package.json:6
- JavaScript dependencies are not locked test/interop/package.json:9
- Duplicated block (6 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:116
- Duplicated block (6 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:134
- Duplicated block (6 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:148
- Duplicated block (6 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:205
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2 locations) javascript/net/grpc/web/grpcwebclientbase_test.js:111
- Duplicated block (10 lines × 2 locations) javascript/net/grpc/web/grpcwebclientreadablestream.js:411
- Duplicated block (10 lines × 2 locations) src/typescript/grpcwebclientbase.ts:277
- Duplicated block (8 lines × 2 locations) javascript/net/grpc/web/grpcwebclientbase_test.js:98
- Duplicated block (8 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:93
- Duplicated block (8 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:226
- Duplicated block (7 lines × 2 locations) javascript/net/grpc/web/grpcwebclientbase_test.js:173
- Duplicated block (7 lines × 2 locations) src/typescript/grpcwebclientbase_test.ts:196
- Duplicated block (7 lines × 2 locations) src/typescript/grpcwebstreamparser_test.ts:109
- GrpcWebClientReadableStream.constructor (cyclomatic 34) javascript/net/grpc/web/grpcwebclientreadablestream.js:71
- GrpcWebClientReadableStream.constructor (cyclomatic 34) src/typescript/grpcwebclientreadablestream.ts:110
- REDACTED
- REDACTED
- MethodTooLong: GrpcWebClientReadableStream.constructor javascript/net/grpc/web/grpcwebclientreadablestream.js:71
- MethodTooLong: GrpcWebClientReadableStream.constructor src/typescript/grpcwebclientreadablestream.ts:110
- Duplicated block (13 lines × 2 locations) src/typescript/grpcwebclientreadablestream.ts:232
- Duplicated block (13 lines × 2 locations) src/typescript/grpcwebclientreadablestream.ts:281
- Duplicated block (11 lines × 2 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:66
- Duplicated block (11 lines × 2 locations) src/typescript/grpcwebstreamparser_test.ts:82
- Complex function (anonymous) (cyclomatic 15, cognitive 18) javascript/net/grpc/web/grpcwebclientreadablestream.js:227
- Complex function (anonymous) (cyclomatic 15, cognitive 18) src/typescript/grpcwebclientreadablestream.ts:206
- GrpcWebStreamParser.parse (cyclomatic 19) javascript/net/grpc/web/grpcwebstreamparser.js:176
- GrpcWebClientReadableStream.constructor (cognitive 72) javascript/net/grpc/web/grpcwebclientreadablestream.js:71
- GrpcWebClientReadableStream.constructor (cognitive 70) src/typescript/grpcwebclientreadablestream.ts:110
- parse (cognitive 22) javascript/net/grpc/web/grpcwebstreamparser.js:176
- StreamBodyClientReadableStream.setUnaryCallback (cognitive 19) src/typescript/streambodyclientreadablestream.ts:72
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplicated block with local edits (130 matched lines × 2 locations) javascript/net/grpc/web/grpcwebclientbase_test.js:202
- Duplicated block with local edits (104 matched lines × 2 locations) javascript/net/grpc/web/statuscode.js:150
- Duplicated block with local edits (102 matched lines × 2 locations) javascript/net/grpc/web/grpcwebclientbase.js:228
- Duplicated block with local edits (91 matched lines × 2 locations) javascript/net/grpc/web/grpcwebclientreadablestream.js:235
- Duplicated block (28 lines × 2 locations) src/typescript/grpcwebclientreadablestream.ts:431
- Duplicated block (23 lines × 2 locations) src/typescript/grpcwebclientbase_test.ts:172
- Duplicated block (18 lines × 2 locations) javascript/net/grpc/web/grpcwebclientbase_test.js:152
- Duplicated block (17 lines × 2 locations) src/typescript/grpcwebstreamparser_test.ts:43
- Duplicated block (15 lines × 2 locations) src/typescript/grpcwebclientbase_test.ts:126
- Duplicated block with local edits (14 matched lines × 2 locations) src/typescript/streambodyclientreadablestream.ts:324
- Duplicated block (12 lines × 4 locations) src/typescript/grpcwebclientbase_test.ts:99
- Duplicated block (11 lines × 3 locations) javascript/net/grpc/web/grpcwebclientbase_test.js:62
- Duplicated block (11 lines × 5 locations) src/typescript/grpcwebclientbase_test.ts:68
- Duplicated block (10 lines × 4 locations) src/typescript/grpcwebclientbase_test.ts:85
- Duplicated block (8 lines × 4 locations) javascript/net/grpc/web/grpcwebstreamparser_test.js:56
- Duplicated block (6 lines × 5 locations) javascript/net/grpc/web/grpcwebclientbase.js:26
- Duplicated block (6 lines × 3 locations) src/typescript/grpcwebstreamparser_test.ts:194
- Complex function (anonymous) (cyclomatic 19, cognitive 53) javascript/net/grpc/web/grpcwebclientreadablestream.js:140
- Complex function (anonymous) (cyclomatic 19, cognitive 51) src/typescript/grpcwebclientreadablestream.ts:116
- Complex function constructor (cyclomatic 15, cognitive 14) javascript/net/grpc/web/grpcwebclientbase.js:59
- Complex function parse (cyclomatic 13, cognitive 11) src/typescript/grpcwebstreamparser.ts:118
- Complex function parse (cyclomatic 11, cognitive 9) javascript/net/grpc/web/grpcwebstreamparser.js:176
- src/typescript/grpcwebclientbase_test.ts: 453 lines of code src/typescript/grpcwebclientbase_test.ts:1
- src/typescript/grpcwebclientreadablestream.ts: 438 lines of code src/typescript/grpcwebclientreadablestream.ts:1
- src/typescript/grpcwebclientbase.ts: 434 lines of code src/typescript/grpcwebclientbase.ts:1
- javascript/net/grpc/web/grpcwebclientreadablestream.js: 416 lines of code javascript/net/grpc/web/grpcwebclientreadablestream.js:1
- The declared test suite includes a file that cannot be loaded packages/grpc-web/test/tsc-tests/client01.ts:20
- Dead file (~37 LoC) packages/grpc-web/externs.js
- Dead file (~1 LoC) packages/closure-wrapper/empty.js
- Unused dependency 'google-protobuf'
Minor — 35 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file scripts/release_notes.py:1
- Orphaned file javascript/net/grpc/web/statuscode.js:1
- Orphaned file javascript/net/grpc/web/abstractclientbase.js:1
- Orphaned file javascript/net/grpc/web/methoddescriptor.js:1
- Orphaned file javascript/net/grpc/web/clientreadablestream.js:1
- Orphaned file packages/grpc-web/scripts/gen_test_htmls.py:1
- Orphaned file javascript/net/grpc/web/interceptor.js:1
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No SAST REDACTED:7
- No dependency-update automation net/grpc/gateway/examples/echo/commonjs-example/package.json:6
- No rollback/health safety
- Duplicated predicate javascript/net/grpc/web/grpcwebstreamparser.js:185
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 1 finding(s)
- doc comments repeat the names javascript/net/grpc/web/grpcwebclientbase.js:363
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-767fb489cb03402da08a8a00cd8f4185/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-767fb489cb03402da08a8a00cd8f4185/tree.json --exit-code 0 --source . | 1 | 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 . | 17 | 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/** . | 3 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 54 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 |