MIT licensing, a changelog, release notes, and no install-time scripts provide useful transparency. The repository is not archived or deprecated, but its tiny footprint and absent security policy leave little evidence of ongoing support.
38%
Total Score
0
67
75
Only two releases were published, with the latest more than eight years ago and none in the last 12 months. This is strong evidence of abandonment risk despite the package's stable version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.
Two stars and two forks indicate a very small user and contributor footprint. Low popularity is supporting evidence rather than a verdict, but it offers little compensating confidence for the maintenance gap.
The linked repository is not archived, which is a modest positive; however, its last push was more than eight years ago, so this does not offset the stale maintenance evidence.
The repository has no security policy. For a package that may be deployed as an application framework, this weakens vulnerability-reporting transparency and is not compensated by the available repository signals.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
enolaphp/utils Version v1.0.1 | — | — |
enolaphp/framework Version v1.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.