geekcms/packagesmanager

Release historydanger

The package has made no release in nearly 7 years: its latest release was July 2019, with no releases in the last 12 months. Four total releases provide some history but do not offset the prolonged inactivity.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release gap. This is strong evidence of abandonment risk.

Repo popularitycaution

The repository has only 2 stars and 0 forks, indicating very limited adoption. Popularity is supporting evidence rather than decisive proof, but it adds to the maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That modestly reduces assurance without independently making the package unsafe to depend on.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities should be reported. This is a secondary hygiene gap beside the more serious maintenance concern.