This is a healthy, actively maintained release with a strong release history: 162 releases over roughly 5.6 years, 33 releases in the last 12 months, and a latest release published today. It is stable, not deprecated, clearly licensed, linked to a matching organization-owned repository, and includes source, tests, and build metadata without install-time lifecycle scripts. The main concerns are that all 15 recent commits came from one contributor, the repository has no security scanning or security policy, and the repository has negligible public popularity and issue activity; these reduce resilience and transparency but are partly offset by the organization's project backing and continued release and commit activity.
82%
Total Score
90
100
94
100
One contributor made all 15 commits in the last three months, creating a real continuity risk. Because the repository is owned by an organization, maintenance can potentially be handed off, so this is a caution rather than a severe abandonment signal.
Composer build tooling is present, but no security scanning tools were detected. The missing security automation is a hygiene gap, not evidence of package unfitness on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
getpop/engine Version ^19.2.4 | — | — |
pop-cms-schema/schema-commons Version ^19.2.4 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.