zaphyr-org/validate
Its documentation and release notes make integration clearer, while organization backing provides some continuity. Build pinning and formal security disclosure remain weaker.
65%
Total Score
67
100
88
75
Health Score Breakdown
The latest registry release was about 18 months ago, with no releases in the last 12 months; this is partly offset by one repository commit in the last three months but still indicates a slow release cadence.
All recent commits came from one contributor; organization ownership offers some handoff capacity, but no second active contributor is shown to reduce the immediate concentration risk.
Only one commit was recorded in the last three months, showing limited recent development activity even though the repository has not been abandoned outright.
The project uses Composer, but no security-scanning tooling was detected, leaving a modest transparency and maintenance gap.
No repository security policy was found, so the project provides less formal guidance for reporting and handling vulnerabilities than a more mature dependency would.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 merloxx |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 symfony/yaml Version ^6.2 | — | — |
zaphyr-org/utils Version ^2.2 | — | — |
zaphyr-org/translate Version ^2.0 | — | — |
egulias/email-validator Version ^4.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 3 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.