The package is licensed, has no install scripts, and has a small, transparent source tree. The repository also does not clearly identify the package, which makes provenance less certain.
35%
Total Score
0
63
75
Only one release exists, published about 9 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the repository remaining available.
There were no commits and no active maintainers in the last 3 months, reinforcing the long period without a release and materially increasing abandonment risk.
The repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less certain, even though the repository is under the same namespace.
Composer is used for the build, but no security scanning tools are present. The missing scanning is a modest transparency and maintenance gap, not evidence of maliciousness.
The repository is not archived, but its last push was about 5 years ago, which is consistent with the inactive release history.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
bricks81/bricks-config Version * | — | — |
bricks81/bricks-loader Version * | — | — |
zendframework/zend-router Version * | — | — |
zendframework/zend-modulemanager Version * | — | — |
zendframework/zend-i18n-resources 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.