The README, release notes, tests, and organization ownership improve transparency. Adding another active contributor and pinning workflow actions would reduce remaining maintenance and build-integrity risk.
72%
Total Score
83
100
93
75
One contributor made all 9 commits in the last 3 months, leaving maintenance dependent on a single person. Organization ownership provides some handoff capacity but does not remove the current concentration.
Composer build tooling is present, but no security-scanning tooling was detected. For this small package that is a transparency and process gap rather than a severe risk.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a limited concern for a small, actively maintained package.
The workflow uses read-only permissions and the audit completed cleanly with no untrusted checkouts or script injection findings. All 3 of 3 action references are unpinned, leaving avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^2.0 | — | — |
componenta/app Version ^4.0.0 || ^5.0.0 | — | — |
componenta/scope Version ^1.0 | — | — |
componenta/config Version ^3.0.0 | — | — |
componenta/templater Version ^1.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.