mitoop/laravel-jpush
The package is clearly identified, has a matching MIT license, and avoids install-time scripts. It has no tests or security policy, while releases and repository commits stopped about three years ago.
45%
Total Score
33
100
78
75
Health Score Breakdown
The package has four releases, all clustered on August 2, 2023, and none in the last 12 months. With the latest release about three years ago, this is strong evidence of abandonment risk.
There were zero commits and zero active maintainers in the last three months. Combined with the old last release, this materially increases the risk that compatibility and fixes are no longer maintained.
The package and repository are owned by the same individual account, so the source linkage is coherent. Individual ownership offers less visible organizational continuity than an organization-backed project.
There are no open issues or pull requests and no recent issue or pull-request activity. While tidy, this also provides no evidence of an active maintenance community.
The repository has 11 stars and 4 forks, showing some external use but limited adoption. Popularity is supporting evidence and cannot counter the lack of recent maintenance.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 mitoop |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 jpush/jpush Version ^3.6 | — | — |
illuminate/queue Version ^9|^10 | — | — |
illuminate/support Version ^9|^10 | — | — |
Weekly Downloads
Info
- Last Published
- 3 years ago
- Created
- 6 years 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.