#
solhint
Here are 17 public repositories matching this topic...
JetBrains IDEA plugin to provide Solhint code verification
jetbrains
linter
ethereum
dapp
smart-contracts
ast
cryptocurrency
solidity
jetbrains-ides
security-scanner
solhint
-
Updated
Jan 3, 2018 - Kotlin
PROJECT MOVED TO https://github.com/protofire/solhint
linter
ethereum
dapp
smart-contracts
ast
developer-tools
solidity
code-quality
security-scanner
solhint
-
Updated
Jul 15, 2020 - JavaScript
Implement integration of Solhint linter to Atom editor
atom
security-audit
linter
ethereum
dapp
smart-contracts
ast
atom-package
solidity
atom-linter
solhint
-
Updated
Jun 19, 2018 - JavaScript
solhint plugin for linting function modifiers. Ensure modifiers are present in certain files, contracts, and methods with flexible matching.
-
Updated
Mar 26, 2021 - JavaScript
Buidler plugin for running solhint
-
Updated
Apr 6, 2019
Watch your repo and run Solhint on every change
-
Updated
Oct 12, 2018 - JavaScript
Smart contracts for basketcoin.
-
Updated
May 21, 2021 - Solidity
This project implements a "multi signature wallet" which, through a Solidity smart contract that allows the creation of a wallet defining a number of owners addresses and a number of confirmations required by these owners to be able to execute a transaction.
-
Updated
Apr 1, 2022 - Solidity
Template for smart contracts development with Solidity and TypeScript using Hardhat
-
Updated
Feb 7, 2022 - TypeScript
-
Updated
Feb 12, 2022 - TypeScript
This project implements a basic voting DAO smart contract for research purposes to understand its inner workings. This is by no means a complete implementation. It also includes an ERC-20 contract to be used as a DAO governance token.
-
Updated
Apr 1, 2022 - Solidity
Improve this page
Add a description, image, and links to the solhint topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the solhint topic, visit your repo's landing page and select "manage topics."


Some file is importing something from some test file. This means that we have to include the test directory in the published package, but besides that it's just a bad idea. I haven't looked into it, but it's probably easy to fix.