Clear organizational ownership, matching repository details, and a documented security policy support ongoing stewardship. The build uses Composer, but no security scanning is configured and two of three workflow references are unpinned.
72%
Total Score
67
100
94
88
No commits and no active maintainers were recorded in the last three months. Although the repository was pushed recently and a release exists, the measured development inactivity lowers confidence in near-term maintenance.
There are three open issues and three open pull requests, but no issues or pull requests were opened or closed in the last month. This is consistent with the broader sign of slower recent activity.
Composer build tooling is present, but no security scanning tools were detected. This is a maintenance and assurance gap, not evidence that the package is unsafe.
All three workflows were analyzed with no audit findings, dangerous triggers, or write-wide permissions. Two of three action references are unpinned, creating a limited reproducibility and supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
brick/varexporter Version ^0.5.0 || ^0.4.0 || ^0.6.0 || ^0.7.0 | — | — |
laminas/laminas-stdlib Version ^3.18.0 | — | — |
webimpress/safe-writer Version ^2.2.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.