A long project history, clear licensing, release notes, and organization backing support continued adoption. Recent repository activity is thin, and workflow permissions and action pinning need tighter hygiene.
68%
Total Score
67
100
88
The package has been available for about 6 years and has 82 releases, but only one release was published in the last 12 months, indicating a slower release cadence.
No commits or active maintainers were recorded during the last three months, which is a meaningful maintenance concern for a dependency even though the repository is not archived.
The repository has three open issues and four open pull requests, with one new pull request but no merged pull requests in the last month; this suggests limited recent throughput rather than severe neglect.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
All three workflows were analyzed with no audit findings or untrusted checkouts. However, one workflow grants top-level write permissions and two of three action uses are unpinned, so workflow hygiene is only partly strong.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
laminas/laminas-code Version ^4.7.1 | — | — |
laminas/laminas-stdlib Version ^3.3.1 | — | — |
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.