Repository navigation
v2.2.0-rc.1 #450
v2.2.0-rc.1
#450
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
cldk v2.2.0-rc.1
This release candidate adds the Go dataflow surface. Go analyses can now answer the same control-flow, data-flow, slice and taint questions as Python, Java and TypeScript.
Breaking changes
None.
Highlights
CLDK.go(...)now exposesget_cfg/get_cdg/get_ddg,resolve_callable/resolve_value,slice_backward/slice_forward/backward_cone,reaches/paths_between,flows_to_call/flows_to_argument,taint,get_external_symbols,get_degradedanddescribe. The signatures are the same as Python's. The local backend and the Neo4j backend give the same answers (feat(go): consume the L3/L4 dataflow substrate (models, accessors, both backends) #444).-a 2. For the dataflow accessors, useanalysis_level="system_dependency_graph".database/sql.DB.Queryhas real ports, so a flow goes through it. This makes library calls usable as taint sinks.get_degraded()is not empty,taintmarks no pair asexhaustedand files oneanalysis_degradeddiagnostic. A path that it returns is still a real may-flow.cldk.analysis.commons.graphs.reach. Each node now enters the next frontier once. Before, an unbounded walk did not stop on large applications.GoType.kindaccepts"alias". Before,-a 1output from a project that declares a type alias failed to parse.Known gaps
locate, the bulk projections, the call-graph verbs,get_imports,get_modulesorget_dependencies(Go: query-surface parity with Python (locate, overviews, call-graph verbs, imports, modules, dependencies) #447).summaryedges are missing. A walk with a depth limit can stop before it finds a path.-a 4payload can be very large (1.78 GB on Kubernetes). At that size, use the Neo4j backend.Upgrade
With the read-only Neo4j backend:
Links
All reactions