Is collective.monkeypatcher safe to use?

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

What is the latest version of collective.monkeypatcher?

The latest version of collective.monkeypatcher is 2.0.1, released 2025-09-24.

Does collective.monkeypatcher have known vulnerabilities?

No known vulnerabilities on the latest version of collective.monkeypatcher.

Is collective.monkeypatcher deprecated?

No, collective.monkeypatcher is actively maintained. Latest release: 2.0.1 (2025-09-24).

What are alternatives to collective.monkeypatcher?

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

What license does collective.monkeypatcher use?

collective.monkeypatcher is licensed under BSD.

collective.monkeypatcher

pypiv2.0.1

Support for applying monkey patches late in the startup cycle by using ZCML configuration actions

License BSDpermissive18 versions1 maintainers7 deps

plone/collective.monkeypatcher

/ 100

Health

safe to use

[email protected] is safe to use (health: 46/100)

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (7)

setuptools zope.configuration zope.event zope.interface zope.schema zope.component;zope.configuration;

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/collective.monkeypatcher