jazor sparkle
58%
Total Score
caution
Usable with caveats: infrequent releases and a single active contributor raise maintenance risk.
The artifact has no README, tests, or changelog; missing tests and changelog are normal for a published PHP artifact, while the missing README modestly reduces consumer documentation.
The registry namespace is jazor, while the linked repository is owned by the individual user sometiny. No organization backing is shown to provide maintenance handoff beyond the current contributor.
Only 4 releases have been published since March 2022, with no releases in the last 12 months and a median interval of about 10 months. The repository's recent push partly offsets abandonment concerns but does not establish a reliable release cadence.
One contributor made 100% of the 3-month commit activity. With project backing identified as an individual user rather than an organization, this creates a meaningful single-maintainer risk.
The repository recorded only 1 commit in the last 3 months from 1 active maintainer. Recent activity is positive, but the very small volume offers limited evidence of sustained maintenance capacity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jazor/core Version >=2.1.0 | — | — |
jazor/illuminate Version >=2.1.0 | — | — |
jazor/think-orm-for-sparkle Version >=2.1.0 | — | — |
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.