The source repository is intact, documented, and backed by an organization, while its small dependency set and MIT declaration reduce adoption friction. No security policy and limited security tooling leave transparency gaps.
58%
Total Score
75
75
50
The latest release was published about two years ago, with no releases in the last 12 months. That is a meaningful maintenance concern for a package developers may need to keep compatible with its host ecosystem.
There were no commits and no active maintainers in the last three months. Combined with the absence of recent releases, this indicates that maintenance may have stopped.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear for adopters.
The assessed release is 5.0.1, while the collected registry metadata reports latest_version as 1.1.1. This inconsistency reduces confidence in the release metadata, even though the version is marked stable and not prerelease.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
craftcms/cms Version ^5.0.0 | — | — |
campaignmonitor/createsend-php Version ^7.0 | — | — |
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.