jyj1993126/cas

Release historydanger

The package has had no release in about nine years: its latest release was in January 2017, with zero releases in the last 12 months. This is strong evidence of abandonment risk despite eight total releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of ongoing maintenance.

Maintainerscaution

Only one registry account has publish access. The linked repository is user-owned rather than organization-backed, so there is little visible redundancy if that maintainer stops supporting the package.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That weakens ongoing transparency and automated risk detection, though it is not evidence of malicious behavior.

Security policycaution

The repository has no security policy. This is a transparency and vulnerability-reporting gap, especially for an authentication package, although it does not by itself show that the code is unsafe.