<commit_before>We want to allow users to play with CSS, which means we need to allow
use of the `class` attribute. HTML like this should be perfectly fine:

```html
<!DOCTYPE html><html><head></head><body>
<a class="blah">u</a>
</body></html>
```

Fortunately, the documents users are making are completely devoid of
JavaScript, so there's no danger in e.g. a jQuery selector going awry
and causing a security breach.<commit_msg>made class_attr test a bit more robust<commit_after>We want to allow users to play with CSS, which means we need to allow
use of the `class` attribute. HTML like this should be perfectly fine:

```html
<!DOCTYPE html><html><head></head><body>
<a class="blah">u</a>
<footer class="gloop">sup</footer>
</body></html>
```

Fortunately, the documents users are making are completely devoid of
JavaScript, so there's no danger in e.g. a jQuery selector going awry
and causing a security breach.
{'fraction_non_alphanumeric': 0.10893246187363835, 'fraction_numerical': 0.0, 'mean_word_length': 5.126666666666667, 'pattern_counts': {'":': 0, '<': 23, '<?xml version=': 0, '>': 23, 'https://': 0, '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': '4657608', 'n_tokens_mistral': 276, 'n_tokens_neox': 253, 'n_words': 127}