Is calender-merger safe to use?

calender-merger has no known vulnerabilities on the latest version (0.0.4). DepScope rates its health at 30/100 (critical risk).

What is the latest version of calender-merger?

The latest version of calender-merger is 0.0.4, released 2016-09-28.

Does calender-merger have known vulnerabilities?

No known vulnerabilities on the latest version of calender-merger.

Is calender-merger deprecated?

No, calender-merger is actively maintained. Latest release: 0.0.4 (2016-09-28).

What are alternatives to calender-merger?

Popular alternatives to calender-merger in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does calender-merger use?

calender-merger is licensed under LGPL.

calender-merger

pypiv0.0.4

Python web server for merging calenders.

License LGPL3 versions1 maintainers2 deps5 weekly dl

niccokunzmann/calender_merger

/ 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

Dependencies (2)

bottle requests

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/calender-merger