Maxime Arthaud

> > some are broken for me, for instance the one for Firefox results > > Could you please give me this link? I just rechecked all Firefox links -...

Hi @IgorInk, This is not currently possible and is unlikely to be implemented soon. The model generation step (which parses the json) does not have information about arguments, it only...

Hi @adityavardhanpadala, You are using `signature_match` with a regex pattern: `"name": "*put*"`. This does not work, `signature_match` does a string equality check. You will have to use the `signature_pattern` constraint....

I'm really confused here. According to your first message, it seems like you have 3 model generator files, Source.json, Sink.json and Propagation.json. The logs in your last message only mention...

fe18ac44ea75ee74a7a060c77a55e975c78e6df4 should prevent this error in the future.

Could you try using `--log-method=` to get the logs of the analysis within the method and send it back to me? Thanks.

Thanks. I think you made a mistake in the models. For `JSONObject.` you have: ``` { "find": "methods", "where": [ { "constraint": "signature_pattern", "pattern": "Lorg/json/JSONObject;\\..*" } ], "model": { "propagation":...

oh my bad, I think you want a propagation from `Argument(1)` to `Argument(0)` ``` "propagation": [ { "input": "Argument(1)", "output": "Argument(0)" } ] ```

Yes this could be a problem. We would have to use a model generator to cover those.

cc @yuhshin-oss we should really document multi source - sink rules.