papaya/module-default-cronjobs

Release historydanger

The package has only two releases, with the latest published in January 2017 and none in the last 12 months. This is strong evidence of abandonment risk for a dependency that may need compatibility or security maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push occurring in January 2017. No newer activity compensates for this maintenance gap.

Licensecaution

No declared license, recognized license file, or repository license file was detected. Although the README mentions GPL v2, the collected license metadata does not establish a machine-readable or file-based license for the package.

Repo toolingcaution

The repository uses Composer for its build workflow, but no security scanning tools were detected. The missing scanning is a modest hygiene concern, not a standalone reason to reject the package.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a secondary transparency gap alongside the absence of recent maintenance.