Skip to content

Conversation

@fvictorio
Copy link
Contributor

Added Slippy, a Solidity linter I'm working on, to the list of Solidity tools.

@github-actions
Copy link

github-actions bot commented Sep 8, 2025

Thank you for your contribution to the Solidity compiler! A team member will follow up shortly.

If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother.

If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix.

Copy link
Contributor

@mehtavishwa30 mehtavishwa30 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contributions to Solidity resources page, @fvictorio. We curate all the resources here carefully based on maturity, usage, and interest around the tooling in the Solidity community and ecosystem.

Since Slippy is a relatively new tool, we would like to take some time to observe how it grows and add it later based on feedback from our surveys. I will be closing this PR on the above grounds for now.

@clonker clonker closed this Sep 15, 2025
@fvictorio
Copy link
Contributor Author

Hi @mehtavishwa30, it's been a couple of months now. Slippy has been adopted by a few serious projects and popular templates and I'm very actively maintaining it. Would you be open to including it now?

Btw, this list also includes ethlint, which hasn't had a new version in six years (!), doesn't work with new versions of Solidity, and basically no one uses. Maybe Slippy doesn't have the level of adoption that it needs to be included, but in that case I think ethlint should be dropped from the list, because it's clearly a worse tool to recommend to users.

@clonker clonker reopened this Dec 9, 2025
@clonker
Copy link
Member

clonker commented Dec 9, 2025

Hey @fvictorio, we revisited the topic internally and will merge your suggestion. Although it seems like our spellchecker is tripping up over Slippy (slipping, so to say...). Mind adding the Slippy line to codespell_whitelist.txt? That should fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants