aharabara/habarnam
The MIT license, matching repository, and repository tests provide useful foundations, but the single registry maintainer and absent security policy add transparency concerns. Treat this as a legacy dependency whose compatibility and maintenance burden require careful ownership.
42%
Total Score
25
50
75
50
Health Score Breakdown
The latest release was in June 2019, with no releases in the last 12 months. That long release gap materially increases abandonment and compatibility risk.
There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for a prolonged period.
The package has eight runtime dependencies, including several PHP extensions and a native ncurses requirement; this creates a meaningful setup and portability burden for consumers.
Only one account has registry publish access. The matching user-owned repository provides some ownership clarity, but the publishing base remains thin.
Composer is used as a build tool, but no security scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 aharabara |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 analog/analog Version ^1.0 | — | — |
vlucas/phpdotenv Version ^3.3@dev | — | — |
symfony/css-selector Version ^4.2 | — | — |
sabberworm/php-css-parser Version ^8.3 | — | — |
Weekly Downloads
Info
- Last Published
- 7 years ago
- Created
- 7 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.