Its BSD-3-Clause license, README, matching repository, and simple dependency profile provide useful transparency. The repository is not archived or deprecated, but it has no security policy or scanning.
42%
Total Score
0
100
75
75
The latest release was about nine years ago, and there were no releases in the last 12 months. This is strong evidence that the package is no longer actively maintained.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and elevated abandonment risk.
The repository has zero stars, one fork, and one watcher, indicating very limited visible adoption. Popularity is supporting evidence, so this reinforces but does not determine the maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. That is a modest hygiene gap, not evidence that the release is unsafe by itself.
The repository has no security policy, leaving vulnerability-reporting and disclosure expectations undocumented. This is a transparency and maintenance weakness for a package handling cloud-service integrations.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
zf1/zend-xml Version self.version | — | — |
zf1/zend-service Version self.version | — | — |
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.