codesinging/think-sae

Release historydanger

The package has had no release in nearly six years despite being established for over six years, and there were no releases in the last 12 months. This strongly suggests the integration is no longer actively maintained.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the nearly six-year gap since the last release. This is the main maintenance and abandonment risk.

Repo popularitycaution

The repository has only 2 stars and 1 fork, providing little evidence of a broad support community. Low popularity alone is not disqualifying, but it offers little compensation for the inactivity.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. This is a transparency and maintenance gap, though the small package and lack of workflows limit its practical severity.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more because the project also shows no recent maintenance activity.