Clear licensing, tests, and documentation make adoption easier. The single-maintainer base, absent security tooling, and no commits in three months leave maintenance and response capacity uncertain.
63%
Total Score
50
100
86
75
Only one registry maintainer is listed, leaving limited visible publishing redundancy for a user-owned project and increasing dependence on one person’s availability.
Five releases arrived within the last 12 months, with a median interval of about four days, but the latest release was roughly four months ago, suggesting activity has paused recently.
The repository had zero commits and zero active maintainers in the last three months. Combined with the roughly four-month gap since the latest release, this is a meaningful maintenance concern.
Composer build tooling is present, but no security-scanning tools were detected. That is a hygiene gap for a package handling form and API integrations, though it is not severe by itself.
The repository has no security policy, leaving no documented path for reporting vulnerabilities or describing response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mzur/kirby-uniform Version ^5.0 | — | — |
mosparo/php-api-client Version ^1.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.