Documentation, repository tests, release notes, and a security policy provide useful project visibility. Maintenance is concentrated in one contributor, and the project is very new with no security scanning; organization backing partly offsets that risk.
65%
Total Score
83
100
79
100
The package is only 46 days old and has just two releases, both published within minutes of each other. This provides little evidence of long-term maintenance or release stability.
All nine recent commits came from one contributor, leaving maintenance dependent on a single individual. Organization backing provides some ability to hand work off, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools were detected. That is a maintenance and assurance gap for an SDK handling authentication and encryption.
Version v0.1.1 is not a stable-major release, so its API and behavior may still change materially despite not being marked prerelease.
The workflow is fully analyzed, uses read-only permissions, and has no detected injection or high-severity findings. However, all 7 action references are unpinned, so build inputs can change without a reviewed commit.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/clock Version ^1.0 | — | — |
psr/http-client Version ^1.0 | — | — |
psr/http-factory Version ^1.0 | — | — |
psr/http-message Version ^2.0 | — | — |
php-http/discovery Version ^1.19 | — | — |
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.