Documentation and tests are in place, with a clear license and no install-time scripts. The project is still very young, and maintenance depends entirely on one contributor with no security policy or scanning.
62%
Total Score
50
100
88
75
The repository is owned by the same individual namespace that publishes the package, and the owner type is User. This confirms consistency but provides no organizational maintenance capacity.
The package is only 42 days old and has two releases, with the latest released about 41 days ago. This is too little history to demonstrate durable maintenance, though the short interval between releases shows an active initial launch.
One contributor made all three recent commits, so maintenance currently has a single point of failure. The repository is user-owned rather than organization-owned, providing no shown backing to offset that concentration.
There were three commits in the last three months, all during the package's brief lifetime. Activity exists, but there is not enough history to establish sustained maintenance.
Composer build tooling is present, but no security scanning tools were detected. That is a process gap for a package handling authorization behavior, though it is not evidence of a defect by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
silber/bouncer Version ^1.0.2 | — | — |
illuminate/database Version ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/container Version ^11.0 || ^12.0 || ^13.0 | — | — |
workerman/webman-framework Version ^2.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.