juzaweb/core
Clear documentation, tests, and release notes improve day-to-day integration. Workflow references are not pinned, and the project lacks a security policy or security scanning.
68%
Total Score
67
50
89
50
Health Score Breakdown
The release declares 22 runtime dependencies, including several framework and service integrations. This increases maintenance surface and transitive dependency exposure, though it is consistent with a CMS core package.
One contributor made all recent commits, so maintenance is fully concentrated in a single person with no demonstrated recent handoff capacity.
Only 1 commit was recorded in the last 3 months, indicating limited recent development activity despite the frequent registry releases.
The repository has 2 stars and 1 fork, providing little external adoption evidence. Popularity is supporting evidence only, so this modestly lowers confidence rather than determining the verdict.
Composer build tooling is present, but no security scanning tools were detected, leaving a meaningful security-maintenance gap for a framework core package.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 doctrine/dbal Version ^4.2 | — | — |
juzaweb/hooks Version ^2.0.3 | — | — |
juzaweb/html-dom Version ^1.0 | — | — |
hassankhan/config Version ^2.2 | — | — |
laravel/socialite Version ^5.5 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 1 year 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.