Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for Embark repos #196

Merged
merged 11 commits into from
Apr 5, 2019
Merged

Added support for Embark repos #196

merged 11 commits into from
Apr 5, 2019

Conversation

rajeevgopalakrishna
Copy link
Contributor

This PR adds support for Embark (https://embark.status.im/) repositories.

On running slither . in the top-level directory of an Embark repo which contains the Embark config file embark.json, Slither detects the presence of this config file and looks for the Embark plugin embark-contract-info in the config file. If found, it installs the plugin and then runs embark build --contracts to compile the contracts in the repo. The plugin gets triggered on the compilation to produce a file which contains AST, ABI, bytecode, etc. of the contracts. The AST files are used by Slither to run its analyses.

To do: Replace the npm install from git to a registered package.

@CLAassistant
Copy link

CLAassistant commented Apr 3, 2019

CLA assistant check
All committers have signed the CLA.

@montyly montyly added this to the 0.6.2 milestone Apr 3, 2019
montyly added 5 commits April 3, 2019 12:29
        - rename force-embark-plugin to embark-overwrite-config
        - add the flag to the slither config file
        - fix incorrect Slither initialization
        - change logic:
                - only install the plugin if config file is written
                - improve error handling
                - do not write contracts ast to an external file
                - do not remove the ast file generated
@montyly montyly merged commit b3cd1ee into dev Apr 5, 2019
@montyly montyly deleted the dev-embark-support branch April 5, 2019 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants