Is cached-markdown-field safe to use?

cached-markdown-field has no known vulnerabilities on the latest version (0.1). DepScope rates its health at 27/100 (critical risk).

What is the latest version of cached-markdown-field?

The latest version of cached-markdown-field is 0.1, released 2021-04-10.

Does cached-markdown-field have known vulnerabilities?

No known vulnerabilities on the latest version of cached-markdown-field.

Is cached-markdown-field deprecated?

No, cached-markdown-field is actively maintained. Latest release: 0.1 (2021-04-10).

What are alternatives to cached-markdown-field?

Popular alternatives to cached-markdown-field in PyPI include: boto3, packaging, urllib3, idna, typing-extensions.

What license does cached-markdown-field use?

cached-markdown-field is licensed under MIT.

cached-markdown-field

pypiv0.1

Cached Markdown field for Django and django-markdownx

License MITpermissive1 versions1 maintainers3 deps

pehala/cached-markdown-field

/ 100

Health

use with caution

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

Low health score (27/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

django django-composite-field django-markdownx

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/cached-markdown-field