Good documentation, tests, and an explicit Apache-2.0 license improve day-to-day adoption. The single-release history and weak workflow controls make long-term maintenance and publishing less reassuring.
57%
Total Score
75
100
88
50
This is the only recorded release, published about 11 months ago, so there is little release history to demonstrate sustained maintenance.
There were no commits and no active maintainers in the last three months, which weakens evidence of ongoing upkeep.
The project uses Composer for builds, but no security scanning tooling was detected, leaving a transparency and maintenance gap for a package handling encrypted connections.
The linked repository has no security policy, which is a meaningful transparency gap for a backend package that handles sensitive connection data.
The only workflow gives every workflow a top-level write token, leaves all 6 action references unpinned, and contains a high-confidence condition that always evaluates true. No untrusted trigger or checkout sink was found, so this is a serious hygiene concern rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^3.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
hawk-hhg/hawki-crypto Version ^0.5.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.