From ddc14b63e8260997d3b9f7891b83a8a844c2e7e0 Mon Sep 17 00:00:00 2001 From: cokeBeer Date: Fri, 16 Sep 2022 19:08:12 +0800 Subject: [PATCH] update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index cf39e4b..c1a353c 100644 --- a/README.md +++ b/README.md @@ -32,7 +32,7 @@ go get -u github.com/cokeBeer/goot ``` ## Use taint analysis -Write code below in your project, e.g `cmd/taint/main.go` +Write code below in the project to be analysed, e.g `cmd/taint/main.go` ```go package main @@ -47,7 +47,7 @@ func main() { // for this project, is "github.com/cokeBeer/goot" runner.ModuleName = "module-name" runner.PassThroughDstPath = "passthrough.json" - runner.CallGraphDstPath = "callgraph.json" + runner.TaintGraphDstPath = "taintgraph.json" runner.Run() } ``` @@ -77,7 +77,7 @@ The rule is ] } ``` -Also, you will get a `callgraph.json` in the same directory\ +Also, you will get a `taintgraph.json` in the same directory\ You can see the json file contains taint edges from one call parameter to another call parameter ```json {