The release is well documented, tested, licensed, and clearly tied to its repository. Its small ownership base, absent recent commits, missing security policy, and completely unpinned workflow actions make long-term maintenance and build integrity less reassuring.
54%
Total Score
50
100
83
63
post-install-cmd and post-update-cmd scripts run during Composer installation or updates, adding execution during dependency operations and requiring extra review.
Only one registry account has publishing access. The repository is user-owned rather than organization-owned, so the narrow publishing base provides limited continuity evidence.
The package and repository are associated with the same user-owned TumTum namespace, but there is no organization backing shown to offset the narrow maintainer base.
Only two releases exist, and there have been no releases in about 19 months. That is a meaningful maintenance concern for a package with a relatively short history.
There were zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
openspout/openspout Version ^4.0 | — | — |
boxblinkracer/phpunuhi Version ^1.9.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.