npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

electusvoting

v2.5.7

Published

Standard implementation and interface for Voting

Downloads

34

Readme

Voting

npm version

Gitter chat

CircleCI

Greenkeeper badge

codecov

Install

git clone https://github.com/chaitanyapotti/Voting.git
cd Voting
npm install

Contracts

The protocol level contracts use OpenZeppelin extensively for referencing standard EIPs. Electus Voting utilizes OpenZeppelin's implementations for EIP-165. Please refer to OpenZeppelin's github page here

truffle

To use with Truffle, first install it and initialize your project with truffle init.

npm install -g truffle
mkdir myproject && cd myproject
truffle init

Installing Voting Framework

After installing either Framework, to install the Voting library, run the following in your Solidity project root directory:

npm init -y
npm install --save electusvoting

After that, you'll get all the library's contracts in the node_modules/electusvoting/contracts folder. You can use the contracts in the library like so:

import 'electusvoting/contracts/poll/IPoll.sol';

contract MyContract is IPoll {
  ...
}

#Linting To lint solidity, use

node ./node_modules/solhint ./contracts/poll/BasePoll.sol

For linting Solidity files you need to run Solhint with one or more Globs as arguments. For example, to lint all files inside contracts directory, you can do:

solhint "contracts/**/*.sol"

To lint a single file:

solhint contracts/MyToken.sol

To disable linting for next line, use

// solhint-disable-next-line

Testing

Unit test are critical to the Electus Voting framework. They help ensure code quality and mitigate against security vulnerabilities. The directory structure within the /test directory corresponds to the /contracts directory. OpenZeppelin uses Mocha’s JavaScript testing framework and Chai’s assertion library. To learn more about how to tests are structured, please reference Voting's Testing Guide.

To run all tests:

Start ganache-cli or other testrpc

npm run test
truffle test

Security

Electus Voting is meant to provide secure, tested and community-audited code, but please use common sense when doing anything that deals with real money! We take no responsibility for your implementation decisions and any security problem you might experience.

The core development principles and strategies that Electus Voting is based on include: security in depth, simple and modular code, clarity-driven naming conventions, comprehensive unit testing, pre-and-post-condition sanity checks, code consistency, and regular audits.

If you find a security issue, please email [email protected].

Contributing

For details about how to contribute you can check the contributing page