bsaliba/utils
The MIT license, matching repository, and release notes provide basic transparency. Missing security policy and scanning leave limited evidence of ongoing oversight for a single-maintainer project.
38%
Total Score
33
70
50
Health Score Breakdown
The package has only one release, published about 9 years and 8 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the release history showing no activity since 2017.
One registry maintainer creates a thin publishing base and limited continuity if that person stops maintaining the package. The linked repository is also owned by an individual.
The project is backed by a personal GitHub account rather than an organization, so there is little visible organizational capacity to compensate for the inactive release and commit history.
Composer build tooling is present, but no security scanning tools are configured. That limits evidence of automated security oversight, though it does not by itself show unsafe behavior.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Bruno Saliba |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 ramsey/uuid Version ^3.5 | — | — |
zendframework/zend-http Version ^2.5 | — | — |
zendframework/zend-crypt Version ^3.2 | — | — |
Weekly Downloads
Info
- Last Published
- 9 years ago
- Created
- 9 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.