The MIT license, focused dependency set, and matching repository make adoption straightforward. Add tests, security scanning, and a security policy before relying on it for remote site control.
55%
Total Score
25
100
88
75
The repository recorded zero commits and zero active maintainers during the last three months. For a package only 150 days old, this is a meaningful abandonment concern, especially alongside the one-day release burst.
The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to compensate for the thin maintenance record.
The package is 150 days old, yet all 8 releases were published within about one hour, followed by no newer release. This launch burst followed by silence weakens confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for an SDK handling remote website-control credentials.
The repository has no security policy. For a package described as cryptographically secure and capable of remotely controlling site status, the missing disclosure path reduces operational transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^10.0|^11.0|^12.0|^13.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.