Is sc.contentrules.groupbydate safe to use?

sc.contentrules.groupbydate has no known vulnerabilities on the latest version (2.0.1). DepScope rates its health at 36/100 (critical risk).

What is the latest version of sc.contentrules.groupbydate?

The latest version of sc.contentrules.groupbydate is 2.0.1, released 2014-03-10.

Does sc.contentrules.groupbydate have known vulnerabilities?

No known vulnerabilities on the latest version of sc.contentrules.groupbydate.

Is sc.contentrules.groupbydate deprecated?

No, sc.contentrules.groupbydate is actively maintained. Latest release: 2.0.1 (2014-03-10).

What are alternatives to sc.contentrules.groupbydate?

Popular alternatives to sc.contentrules.groupbydate in PyPI include: boto3, packaging, urllib3, certifi, idna.

What license does sc.contentrules.groupbydate use?

sc.contentrules.groupbydate is licensed under GPLv2.

sc.contentrules.groupbydate

pypiv2.0.1

A Plone content rules action that creates a chronological archive.

License GPLv2strong copyleft13 versions1 maintainers0 deps43 weekly dl

/ 100

Health

use with caution

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

Moderate health score (36/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/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/sc.contentrules.groupbydate