jmose/command-scheduler-bundle

Release historydanger

The package has made no release in roughly six years, despite 21 releases overall. That long gap materially raises abandonment and compatibility risk.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old registry release, this points to weak current maintenance.

Repo issue activitycaution

There are 28 open issues and 13 open pull requests, while none were opened or closed in the last month. The backlog and inactivity add to the maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.