pdatepicker/persian-datepicker
Clear MIT licensing and a substantial README make integration easier. Composer lifecycle hooks, a single registry maintainer, and unpinned workflow actions add maintenance and build-hygiene concerns.
45%
Total Score
33
100
81
50
Health Score Breakdown
The package is about 18 months old but has had no release in the last 12 months; its 13 releases were tightly clustered within minutes, leaving no evidence of sustained release maintenance.
There were zero commits and zero active maintainers in the last three months, consistent with the broader absence of recent releases and indicating a stalled project.
The package declares four Composer lifecycle scripts, including install and update hooks. These increase installation complexity and deserve review, although the signal does not establish harmful behavior.
Only one account has registry publish access. Because the repository owner is a user rather than an organization, this leaves limited visible publishing redundancy.
The repository is owned by a user account rather than an organization, providing no demonstrated organizational backing to offset the thin maintenance footprint.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 ViraCoding |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 morilog/jalali Version ^3.4 | — | — |
illuminate/support Version * | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.