The project has a strong release record, clear documentation, tests, and an exact GitHub repository match. Recent repository activity is paused, and there is no published security policy, so ongoing maintenance depends heavily on one maintainer.
68%
Total Score
50
100
94
75
Only one registry account has publish access. That is a resilience concern for a user-owned project, though the release history shows that this maintainer has continued publishing.
The repository is owned by a user account rather than an organization, so the single registry maintainer is not explained by organization-backed publishing. This supports treating the thin maintainer base as a real resilience concern.
The repository recorded zero commits and zero active maintainers during the last 3 months. This is a meaningful maintenance concern, although the recent release history shows the project was active over the broader period.
There were no new or closed issues or pull requests in the last month, with five issues remaining open. This suggests limited current collaboration, but it is weaker evidence than the lack of recent commits.
The repository has 1 star, 0 forks, and 4 watchers, indicating a very small visible user base. Popularity is supporting evidence rather than a verdict, so this only modestly lowers confidence in long-term community support.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
monolog/monolog Version >=2.7 | — | — |
mistralys/application-utils Version >=3.2.0 | — | — |
giggsey/libphonenumber-for-php Version ^8.12 | — | — |
mistralys/application-localization Version >=2.1.2 | — | — |
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.