sashagm/notification
Tests, documentation, licensing, and a matching source repository provide a solid baseline. The project has had no registry release in two years and no recorded commits in the last three months, so maintenance should be watched closely.
62%
Total Score
50
100
88
88
Health Score Breakdown
Only one registry account has publish access. That is not conclusive about project health, but combined with the lack of recent commits it leaves a thin apparent maintenance base.
The registry namespace and repository are owned by the same individual account, providing direct ownership alignment but no organizational backing to offset the thin maintainer base.
The package has 20 releases, but none in the last 12 months; its latest release was in September 2024, indicating a prolonged release gap for a package with a two-year history.
The repository recorded zero commits and zero active maintainers in the last three months, which is a concrete sign of currently inactive development and raises abandonment risk.
Composer build tooling is present, but no security-scanning tool was detected; this is a modest transparency and hygiene gap rather than evidence of unsafe code.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 sashagm |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 twilio/sdk Version ^7.5 | — | — |
irazasyed/telegram-bot-sdk Version ^3.13 | — | — |
laravel-notification-channels/telegram Version ^4.0 || ^5 | — | — |
Weekly Downloads
Info
- Last Published
- 2 years ago
- Created
- 3 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.