netosts/laravel-fcm-notifications
Clear documentation, licensing, and a matching source repository make adoption easier. The project has had no commits or releases for about one year, and it lacks a security policy and automated security scanning, leaving future fixes uncertain.
58%
Total Score
50
88
50
Health Score Breakdown
The package had 12 releases, but none in the last 12 months; its latest release was about one year ago. This indicates a meaningful maintenance gap despite a previously active release period.
The repository recorded 0 commits and 0 active maintainers during the last 3 months, consistent with the roughly one-year release gap. No provided activity signal compensates for this pause.
Composer build tooling is present, but no security-scanning tools are configured. This is a hygiene gap that adds uncertainty alongside the lack of recent maintenance.
The repository has no security policy, which reduces transparency for reporting and handling vulnerabilities in a package that manages push-notification credentials and tokens.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 netosts |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 laravel/framework Version ^10.0|^11.0|^12.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 1 year 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.