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

feat: printer to expose low level gathered information #232

Open
yxliang01 opened this issue May 9, 2019 · 2 comments
Open

feat: printer to expose low level gathered information #232

yxliang01 opened this issue May 9, 2019 · 2 comments

Comments

@yxliang01
Copy link
Contributor

yxliang01 commented May 9, 2019

This feature request is to propose exposing low level information generated by Slither via printers. Slither is a very useful static analysis framework for Solidity. Currently, it can be used by other Python scripts as a library that the Python scripts can freely access low level information generated by Slither. One example would be https://raw.githubusercontent.com/crytic/slither/master/utils/upgradeability/check_initialization.py . While there are many printers available currently for exposing different kind of information, as far as I know, there is no printer that exposes all gathered information by Slither. So, this issue is about exposing all of them at once to facilitate future processing to be done in other programming languages or systems.

Thanks

@montyly
Copy link
Member

montyly commented May 10, 2019

Hi @yxliang01, this is a great idea!

We are actually looking at exposing some of Slither internal information through a printer, so external tooling can take advantage of Slither, without having to interface to Python.

The main issue is that it's unclear what information we will output. It's likely going to match our internal needs first, but we would love to hear your suggestions or to know what you need. Feel free to join our slack (#ethereum) if you want to discuss it.

@yxliang01
Copy link
Contributor Author

@montyly Actually, a new input argument specifying what information the user is looking for would be cool. Maybe something like solc standard-json input or lightweight input specification would be good. Outputting all raw analyzed information might be too much. I would join the slack channel when I have more time :) Also, happy to see this happen!

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

No branches or pull requests

2 participants