The package is clearly licensed, matches its repository, and documents basic usage. Its two releases arrived in one day, with no release or repository activity for about seven years, leaving maintenance and compatibility uncertain.
38%
Total Score
50
100
78
83
Only two releases were published, both on November 14, 2018, and none appeared in the following years. This sustained inactivity is a substantial abandonment concern despite the package not being deprecated.
The package and repository are owned by the same individual account, providing consistent ownership but no organizational backing signal. The single-owner context offers limited evidence of maintenance capacity.
The repository has zero stars, forks, and watchers, so there is little visible community support or adoption evidence. Popularity is supporting evidence, but this reinforces the maintenance uncertainty.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. This is a modest transparency and hygiene gap rather than a decisive risk.
The repository has no security policy. For a small package this is a hygiene gap, but it matters more alongside the long period without observable maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
zendframework/zend-db Version ^2.5 | — | — |
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.