tureki/phpcc

Repo commit activitydanger

There were no commits or active maintainers in the last three months, and the repository was last pushed about 8 years ago. This is strong evidence of inactive maintenance.

Release historycaution

Only two releases exist, with the latest about 11 years ago and no releases in the last 12 months. The stable version and available release notes help, but the long release gap raises abandonment risk.

Repo toolingcaution

Composer is used for builds, but no security-scanning tools are present. The missing scanning is a hygiene gap rather than evidence that the package is unsafe by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more for a dependency that has not shown recent maintenance.