<commit_before># Contributing

:+1::tada: We're excited you want to contribute! Read on! :tada::+1:

## Reporting security issues

If you discover a security issue, please **DO NOT** file a public issue, 
instead send your report [privately](https://gitter.im/patrick-steele-idem).

Security reports are greatly appreciated and we will publicly thank you for it.
We currently do not offer a paid security bounty program.

## Reporting other issues

A great way to contribute to the project is to send a detailed report when you
encounter an issue.

Check that [our issue database](https://github.com/marko-js/marko/issues)
doesn't already include that problem or suggestion before submitting an issue.
If you find a match, you can use the "subscribe" button to get notified on
updates. Rather than leaving a "+1" or "I have this too" comment, you can add a 
[reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) 
to let us know that this is also affecting you without cluttering the conversation. 
However, if you have ways to reproduce the issue or have additional information that may help
resolving the issue, please leave a comment.

We have an [ISSUE_TEMPLATE](ISSUE_TEMPLATE.md) that will populate your textarea 
when you go to open an issue.  Use the relevant section and remove the rest. 

Please provide as much detail as possible.

## Quick contribution tips and guidelines

This section gives the experienced contributor some tips and guidelines.

### Pull requests are always welcome

Not sure if that typo is worth a pull request? Found a bug and know how to fix
it? Do it! We will appreciate it. Any significant improvement should be
documented as [a GitHub issue](https://github.com/marko-js/marko/issues) before
anybody starts working on it.

We are always thrilled to receive pull requests. We do our best to process them
quickly. If your pull request is not accepted on the first try,
don't get discouraged! We'll work with you to come to an acceptable solution.

If you're new to GitHub or open source you can check out this 
[free course](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github) 
on how to contribute to an open source project.

Before submitting your PR, make sure that all new and previous tests pass and that [coverage](https://coveralls.io/github/marko-js/marko?branch=master) has not decreased:
```
npm run test-coverage
```

### Tackling an existing issue

Comment on the issue and let us know you'd like to tackle it.   
We'll assign you to the issue so that we don't duplicate effort.  

If for some reason you aren't going to be able to complete the work, 
let us know as soon as you can so we can open it up for another 
developer to work on.

Here's some to get started with:

- [`bite-sized`](https://github.com/marko-js/marko/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Abite-sized%20no%3Aassignee) issues: great for new contributors
- [`help-wanted`](https://github.com/marko-js/marko/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Ahelp-wanted%20no%3Aassignee) issues: won't be tackled in the near future by the maintainers... we need your help!
- [un-assigned](https://github.com/marko-js/marko/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20no%3Aassignee%20) issues: open issues that no one has claimed... yet

## Maintainers

* [<NAME>](https://github.com/patrick-steele-idem) (Twitter: [@psteeleidem](http://twitter.com/psteeleidem))
* [<NAME>](https://github.com/philidem/) (Twitter: [@philidem](https://twitter.com/philidem))
* [<NAME>](https://github.com/mlrawlings) (Twitter: [@mlrawlings](https://twitter.com/mlrawlings))
* [<NAME>](https://github.com/tindli) (Twitter: [@metaCoffee](https://twitter.com/metaCoffee))

## Labels

Once you post an issue, a maintainer will add one or more labels to it.
Below is a guideline for the maintainers and anyone else who is interested 
in what the various labels mean. 

### Type
![](https://img.shields.io/badge/type-bug-dd0000.svg)
![](https://img.shields.io/badge/type-enhancement-0099dd.svg)
![](https://img.shields.io/badge/type-question-99cc00.svg)
![](https://img.shields.io/badge/type-docs-999999.svg)

Every issue should be assigned one of these.

- **bug**: A bug report 
- **enhancement**: A feature request
- **question**: A question about how to use Marko
- **docs**: An issue about documentation

### Scope
![](https://img.shields.io/badge/scope-parser-5500cc.svg)
![](https://img.shields.io/badge/scope-compiler-cc0077.svg)
![](https://img.shields.io/badge/scope-runtime-eebb00.svg)
![](https://img.shields.io/badge/scope-core%20taglib-00cccc.svg)
![](https://img.shields.io/badge/scope-widgets-9900aa.svg)
![](https://img.shields.io/badge/scope-tools-33cc00.svg)

What part of the Marko stack does this issue apply to? In most cases there should only be one of these.

- **parser**: Relates to `htmljs-parser`<commit_msg>Change the color of the tools label<commit_after># Contributing

:+1::tada: We're excited you want to contribute! Read on! :tada::+1:

## Reporting security issues

If you discover a security issue, please **DO NOT** file a public issue, 
instead send your report [privately](https://gitter.im/patrick-steele-idem).

Security reports are greatly appreciated and we will publicly thank you for it.
We currently do not offer a paid security bounty program.

## Reporting other issues

A great way to contribute to the project is to send a detailed report when you
encounter an issue.

Check that [our issue database](https://github.com/marko-js/marko/issues)
doesn't already include that problem or suggestion before submitting an issue.
If you find a match, you can use the "subscribe" button to get notified on
updates. Rather than leaving a "+1" or "I have this too" comment, you can add a 
[reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) 
to let us know that this is also affecting you without cluttering the conversation. 
However, if you have ways to reproduce the issue or have additional information that may help
resolving the issue, please leave a comment.

We have an [ISSUE_TEMPLATE](ISSUE_TEMPLATE.md) that will populate your textarea 
when you go to open an issue.  Use the relevant section and remove the rest. 

Please provide as much detail as possible.

## Quick contribution tips and guidelines

This section gives the experienced contributor some tips and guidelines.

### Pull requests are always welcome

Not sure if that typo is worth a pull request? Found a bug and know how to fix
it? Do it! We will appreciate it. Any significant improvement should be
documented as [a GitHub issue](https://github.com/marko-js/marko/issues) before
anybody starts working on it.

We are always thrilled to receive pull requests. We do our best to process them
quickly. If your pull request is not accepted on the first try,
don't get discouraged! We'll work with you to come to an acceptable solution.

If you're new to GitHub or open source you can check out this 
[free course](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github) 
on how to contribute to an open source project.

Before submitting your PR, make sure that all new and previous tests pass and that [coverage](https://coveralls.io/github/marko-js/marko?branch=master) has not decreased:
```
npm run test-coverage
```

### Tackling an existing issue

Comment on the issue and let us know you'd like to tackle it.   
We'll assign you to the issue so that we don't duplicate effort.  

If for some reason you aren't going to be able to complete the work, 
let us know as soon as you can so we can open it up for another 
developer to work on.

Here's some to get started with:

- [`bite-sized`](https://github.com/marko-js/marko/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Abite-sized%20no%3Aassignee) issues: great for new contributors
- [`help-wanted`](https://github.com/marko-js/marko/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Ahelp-wanted%20no%3Aassignee) issues: won't be tackled in the near future by the maintainers... we need your help!
- [un-assigned](https://github.com/marko-js/marko/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20no%3Aassignee%20) issues: open issues that no one has claimed... yet

## Maintainers

* [<NAME>](https://github.com/patrick-steele-idem) (Twitter: [@psteeleidem](http://twitter.com/psteeleidem))
* [<NAME>](https://github.com/philidem/) (Twitter: [@philidem](https://twitter.com/philidem))
* [<NAME>](https://github.com/mlrawlings) (Twitter: [@mlrawlings](https://twitter.com/mlrawlings))
* [<NAME>](https://github.com/tindli) (Twitter: [@metaCoffee](https://twitter.com/metaCoffee))

## Labels

Once you post an issue, a maintainer will add one or more labels to it.
Below is a guideline for the maintainers and anyone else who is interested 
in what the various labels mean. 

### Type
![](https://img.shields.io/badge/type-bug-dd0000.svg)
![](https://img.shields.io/badge/type-enhancement-0099dd.svg)
![](https://img.shields.io/badge/type-question-99cc00.svg)
![](https://img.shields.io/badge/type-docs-999999.svg)

Every issue should be assigned one of these.

- **bug**: A bug report 
- **enhancement**: A feature request
- **question**: A question about how to use Marko
- **docs**: An issue about documentation

### Scope
![](https://img.shields.io/badge/scope-parser-5500cc.svg)
![](https://img.shields.io/badge/scope-compiler-cc0077.svg)
![](https://img.shields.io/badge/scope-runtime-eebb00.svg)
![](https://img.shields.io/badge/scope-core%20taglib-00cccc.svg)
![](https://img.shields.io/badge/scope-widgets-9900aa.svg)
![](https://img.shields.io/badge/scope-tools-fef2c0.svg)

What part of the Marko stack does this issue apply to? In most cases there should only be one of these.

- **parser**: Relates to `htmljs-parser`
{'fraction_non_alphanumeric': 0.11871961102106969, 'fraction_numerical': 0.018233387358184763, 'mean_word_length': 4.61923733636881, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 52, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1322136', 'n_tokens_mistral': 3309, 'n_tokens_neox': 3044, 'n_words': 1117}