Git and deployment lifecycle notifications for Laravel, delivered to Telegram
70%
Total Score
caution
A brand-new release with one maintainer and fully unpinned workflow actions limits maturity despite strong documentation and tests.
The registry has one publishing maintainer. That is consistent with an individual-owned project, but it leaves limited publishing redundancy.
The repository is owned by an individual account rather than an organization, so there is no demonstrated organizational handoff capacity to offset the concentrated contributor base.
This is the first and only release, published less than a day ago, so there is not yet enough history to demonstrate sustained maintenance.
All five recent commits came from one contributor, so maintenance depends entirely on a single active developer and has a low bus factor.
Composer build tooling is present, but no security scanning tools were detected; this is a modest transparency and maintenance gap for a package handling deployment notifications and secrets.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^10.0 || ^11.0 || ^12.0 | — | — |
guzzlehttp/guzzle Version ^7.2 | — | — |
illuminate/console Version ^10.0 || ^11.0 || ^12.0 | — | — |
illuminate/process Version ^10.0 || ^11.0 || ^12.0 | — | — |
illuminate/routing Version ^10.0 || ^11.0 || ^12.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.