The single-maintainer project has no security policy, and its repository has no recent commit activity. The MIT license, matching repository, release notes, and straightforward dependency set improve transparency, but ongoing maintenance remains uncertain.
58%
Total Score
50
100
93
50
One registry maintainer is a thin publishing base for a package without visible recent development activity. The linked repository is user-owned, so there is no organizational backing shown to offset that concern.
The package has only two releases, with no releases in the last 12 months and about 15 months since version 1.0.1. This indicates limited and currently inactive release maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long period since the latest release. This weakens evidence of ongoing maintenance.
The repository has no security policy, leaving vulnerability-reporting expectations and response procedures undocumented. This is a transparency gap, though it is not evidence of unsafe code by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.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.