advanced-notifications/core
The package includes clear documentation, tests, an MIT license, and no install-time scripts. Its 14 releases were packed into roughly 38 hours, followed by about nine months without commits or releases, and the repository has no security policy or scanning.
58%
Total Score
50
75
75
Health Score Breakdown
All 14 releases occurred within roughly 38 hours, and the latest release was about nine months ago; this suggests an initial burst followed by inactivity.
There were zero commits and zero active maintainers in the last three months, consistent with roughly nine months since the last push and raising abandonment concern.
The repository has zero stars, forks, and watchers. This is weak supporting evidence rather than a verdict, but it provides no external sign of adoption or review.
Composer build tooling is present, but no security-scanning tools were detected, leaving a meaningful maintenance and assurance gap for a package handling notification and token functionality.
The linked repository is not archived, but its last push was about nine months ago, so the unarchived status does not offset the inactivity evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Advanced Notifications Team |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 google/auth Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
laravel/framework Version ^10.0|^11.0|^12.0 | — | — |
spatie/laravel-translatable Version ^6.0 | — | — |
Weekly Downloads
Info
- Last Published
- 10 months ago
- Created
- 10 months 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.