Documentation, licensing, and repository tests are present. The single maintainer, absent security policy, repository name mismatch, and more than five years without a release or commit make this a poor default for new integrations.
38%
Total Score
25
79
75
The latest release was published more than five years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a Laravel integration package.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.
Only one registry account has publish access. That is a modest resilience concern for an apparently user-owned project, but registry access alone does not establish who actively maintains it.
The linked repository is named "fcm" rather than this package and its README does not mention the package. That raises uncertainty about whether the source repository actually belongs to this release.
The repository has no security policy, leaving vulnerability reporting and handling undocumented. This is a transparency gap, although it is less serious than the prolonged inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spatie/enum Version ^2.3 || ^3.0 | — | — |
guzzlehttp/guzzle Version ^6.2 || ^7.0 | — | — |
illuminate/support Version ^5.6 | — | — |
kreait/laravel-firebase Version ^1.3 | — | — |
illuminate/notifications Version ^5.6 | — | — |
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.