Package Health/dizda/onesignal-api-bundle

dizda/onesignal-api-bundle

The MIT license, README, and matching repository make the package easy to inspect and integrate. However, no release has been published since July 2015, and the repository has had no commits in the last three months after last being updated in February 2018. A single maintainer, no security policy, and limited project activity add abandonment risk.

Latest 0.1.5

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, and its latest release was published in July 2015. This long release gap is strong evidence of abandonment risk, despite the package not being registry-deprecated.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. With the repository last pushed in 2018, this indicates sustained inactivity rather than a short pause.

Repo popularity

The repository has only 8 stars and 7 forks, providing little evidence of a broad active user or contributor community. Popularity is supporting evidence, so this reinforces but does not determine the abandonment concern.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. The missing scanning is a hygiene gap, though it is secondary to the much stronger inactivity evidence.

Repository archived

The linked repository is not archived, but it was last pushed in February 2018. The non-archived status is mildly reassuring, while the old update date supports the broader inactivity concern.