Contribution Guidelines

I would love every kind of contribution, we need everyone help to run this project!

Please send your contribution using Github pull requests or just get in touch with me (@jekil).

Thank you for your contribuition!

Quality standard

This is a curated list, not a comprehensive list, so contents should be cool. To stay on the list, tools should adhere to these quality standards:

  • Generally useful to the community

  • Functional and cool

  • Maintained

Adding to this list

Do you want to get a tool listed or add your own tool? Please prepare your pull following some suggestions:

  • Do not add duplicates: search the list before adding a new tool.

  • Make sure the tool is useful before submitting, it should be a maintained or at leats still in use tool.

  • Make an individual pull request for each suggestion.

  • Use the syntax used in the list.

  • List items should be sorted alphabetically.

  • Do not add descriptions too long, few lineas are enough. Be clear, concise and non-promotional.

  • New categories or improvements to the existing categorization are welcome, although it is a good idea to discuss toghever big refactoring.

  • Check your spelling and grammar.

  • Make sure your text editor is set to remove trailing whitespace.

  • The pull request and commit should have a descriptive title.

  • Please write descriptive commit messages.

Edit / Fix the list

Any fix or improvment to the list is welcome, for example:

  • If you have found a typo.

  • If you want to improve a description.

  • If you have any issues accessing a linked tool.

Contributor Covenant Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language

  • Being respectful of differing viewpoints and experiences

  • Gracefully accepting constructive criticism

  • Focusing on what is best for the community

  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances

  • Trolling, insulting/derogatory comments, and personal or political attacks

  • Public or private harassment

  • Publishing others’ private information, such as a physical or electronic address, without explicit permission

  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.


This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.


Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at @jekil. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.


This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at