avram/vokativ
The stable API, MIT licensing, and small dependency footprint make adoption straightforward. However, maintenance has effectively stopped, and the repository has no security policy or scanning, leaving future fixes uncertain.
44%
Total Score
50
100
86
75
Health Score Breakdown
The registry lists one maintainer account. That is a limited publishing base for a user-owned project and increases continuity risk when combined with the lack of recent activity.
The latest release was published in June 2016, about 10 years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having four releases.
There were zero commits and zero active maintainers in the last three months, consistent with the repository having received no push for about eight years. This materially raises abandonment risk.
Composer is used for builds, but no security scanning tools are configured. This is a maintenance and transparency gap, though it is less significant than the prolonged inactivity.
The repository has no security policy. That leaves vulnerability reporting and response expectations unclear, adding a modest transparency concern.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Nemanja Avramovic |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 10 years ago
- Created
- 10 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.