laraveler/geetest

Release historydanger

Only one release has ever been published, in June 2016, 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 no commits and no active maintainers in the last three months, consistent with the package's decade-long release inactivity.

Repo package mentioncaution

The repository name does not match the package name, although its README does mention the package. The README link partly compensates, but the mismatch still reduces source transparency.

Repo toolingcaution

The project uses Composer but has no security-scanning tooling. That is a modest supply-chain hygiene gap, especially alongside the lack of recent maintenance.

Security policycaution

The repository has no security policy. This is a transparency gap for a package handling authentication-related integration, although its small scope limits the impact.