The repository has had no commits in three months, and recent issue and pull-request work has also stopped. Strong tests, release notes, licensing, and security scanning provide useful support, but workflow references are all unpinned and four workflows grant broad write access.
65%
Total Score
50
100
94
75
One registry account has publishing access, which creates a narrow release-access base. The linked repository is owned by the same individual, so this is a genuine single-owner capacity concern rather than an organization-versus-publisher mismatch.
The package and repository are both owned by the same individual account rather than an organization. That aligns ownership but offers limited visible institutional backing for long-term continuity.
The package has existed for over five years with 19 releases, but only one release appeared in the last 12 months. That indicates a slower release cadence and modest maintenance concern.
The repository recorded zero commits and zero active maintainers in the last three months. That is a meaningful abandonment risk, although the recent stable release and non-archived repository provide some counterevidence.
There are 13 open issues and 25 open pull requests, but no new or closed issues and no merged pull requests in the last month. The backlog and lack of recent handling suggest reduced maintenance responsiveness.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
imangazaliev/didom Version ^2.0 | — | — |
composer/installers Version ^2.3 | — | — |
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.