jclg/php-slack-bot

Release historydanger

The latest release was about 8 years ago, with no releases in the last 12 months. Although the package had 7 releases and a previously regular 63-day median interval, the long current gap signals likely abandonment.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the absence of recent registry releases. This provides little evidence of ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The build setup is established, while security-maintenance evidence is limited.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it does not by itself make the package unfit.