ppeerit/think-apicode

Release historydanger

The package has only one release, published in May 2017, with no releases in the last 12 months. That long period without a new release is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged inactivity.

Maintainerscaution

Only one registry maintainer is listed. For this small user-owned project that is plausible, but it creates limited continuity if the maintainer becomes unavailable.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of unsafe code.

Security policycaution

The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a meaningful transparency gap for a dependency, though it does not outweigh the maintenance evidence alone.