direct808/vk
The project has one registry maintainer, no security policy, and no security scanning. Tests, an MIT license, no runtime dependencies, and no install scripts reduce adoption risk, but do not offset the stale project.
35%
Total Score
33
100
78
75
Health Score Breakdown
The package has only two releases, with the latest published over eight years ago and none in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided activity signal compensates for this inactivity.
Only one registry account has publish access. That is a thin publishing base and increases continuity risk, although the repository is owned by the same individual.
The registry namespace and repository owner match, but the owner is an individual rather than an organization. This supports repository identity without providing organizational continuity.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no additional community or maintenance signal.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 direct808 |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 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.