A single user account publishes it, and the workflow leaves all three actions unpinned. Recent releases and a matching, tested repository provide useful continuity.
68%
Total Score
75
50
89
67
Eleven runtime dependencies create a relatively broad dependency surface for a small library, increasing transitive maintenance exposure, though the dependencies are explicitly declared.
Only one registry publishing account is listed. This is a modest resilience concern for continuity, although the repository shows recent releases under the same owner.
The repository recorded zero commits and zero active maintainers in the last three months. This recent inactivity is a meaningful maintenance concern despite the package's recent release history.
The repository has seven stars and two forks, indicating limited external adoption and review. Popularity is supporting evidence rather than a decisive health measure.
Composer is used as the build tool, but no security scanning tooling is reported. This is a hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7 || ^6 | — | — |
nguyenanhung/nusoap Version ^0.9 | — | — |
nguyenanhung/my-debug Version ^4.0 || ^3.0 || ^2.0 | — | — |
nguyenanhung/ip-helper Version ^2.0 || ^1.0 | — | — |
symfony/http-foundation Version ^7.4 || ^6.4.29 || ^5.4.50 | — | — |
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.