orkan/utils
Regular releases, a maintained repository, and clear documentation support ongoing use. The missing security policy and reliance on one active contributor leave continuity and response practices less robust.
70%
Total Score
67
100
94
75
Health Score Breakdown
The repository is owned by an individual user rather than an organization, so the single-contributor concentration has no shown organizational handoff support.
All 7 recent commits came from one contributor, so maintenance continuity depends heavily on a single person.
Composer build tooling is used, but no security-scanning tooling is reported; the missing scanner is a modest transparency and maintenance gap.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Orkan |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 13 days ago
- Created
- 6 years 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.