maykonn/onesignal-laravel

Release historydanger

The latest release was published in December 2016, with no releases in the last 12 months. Nearly ten years without a release is strong evidence of abandonment for a library integration.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release hiatus. This materially increases the risk that compatibility and security issues will remain unaddressed.

Repo popularitycaution

The repository has only one star, one fork, and one watcher, offering little supporting evidence of community review or adoption. Low popularity alone is not decisive, but it provides no counterweight to the inactivity concerns.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a transparency gap, though the small and inactive repository has no evidence of risky automation.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. The absence is more consequential for a package that handles service credentials and API requests.