Is collective.autopublishing safe to use?

collective.autopublishing has no known vulnerabilities on the latest version (1.0.3). DepScope rates its health at 30/100 (critical risk).

What is the latest version of collective.autopublishing?

The latest version of collective.autopublishing is 1.0.3, released 2019-07-18.

Does collective.autopublishing have known vulnerabilities?

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

Is collective.autopublishing deprecated?

No, collective.autopublishing is actively maintained. Latest release: 1.0.3 (2019-07-18).

What are alternatives to collective.autopublishing?

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

What license does collective.autopublishing use?

collective.autopublishing is licensed under GPLv2+.

collective.autopublishing

pypiv1.0.3

Publishes and retracts on effective or expired dates.

License GPLv2+5 versions1 maintainers0 deps62 weekly dl

/ 100

Health

use with caution

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

Moderate health score (30/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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