Is rtf_tokenize safe to use?

rtf_tokenize has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 46/100 (high risk).

What is the latest version of rtf_tokenize?

The latest version of rtf_tokenize is 1.0.1, released 2025-06-28.

Does rtf_tokenize have known vulnerabilities?

No known vulnerabilities on the latest version of rtf_tokenize.

Is rtf_tokenize deprecated?

No, rtf_tokenize is actively maintained. Latest release: 1.0.1 (2025-06-28).

What are alternatives to rtf_tokenize?

Popular alternatives to rtf_tokenize in PyPI include: boto3, packaging, urllib3, certifi, idna.

What license does rtf_tokenize use?

rtf_tokenize is licensed under GNU General Public License v2 or later (GPLv2+).

rtf_tokenize

pypiv1.0.1

Simple RTF tokenizer

License GNU General Public License v2 or later (GPLv2+)2 versions1 maintainers1 deps1,419 weekly dl

benoit-pierre/rtf_tokenize

/ 100

Health

use with caution

[email protected] low health (46/100) — consider alternatives

Moderate health score (46/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

6/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

pytest

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/rtf_tokenize