wazobia/helios-permissions
Healthy and suitable to use, with limited transparency gaps. It has frequent recent releases, active commits from three contributors, tests, and organization backing; the main caveats are no security policy or security scanning and a proprietary license declaration.
78%
Total Score
100
79
75
Health Score Breakdown
The manifest declares a proprietary license, so licensing is explicit, although it does not provide the usual open-source licensing transparency expected for a dependency described as open source.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning lowers maintenance transparency somewhat without indicating that the package is unsafe by itself.
The repository has no security policy. This leaves vulnerability reporting and response expectations undocumented, creating a transparency gap for an authorization-related SDK.
Version 0.11.3 is not a stable major release, but it is not marked prerelease and recent releases have no prerelease share. This is a modest maturity caveat rather than a serious adoption blocker.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 predis/predis Version ^2.2 || ^3.5 | — | — |
illuminate/http Version ^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 2 months ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.