maksa988/vk

Its MIT license, clear README, and single runtime dependency keep adoption straightforward. However, the package and repository have seen no activity for about 11 years, with no tests, security scanning, or security policy, so compatibility and maintenance support are uncertain.

Latest 1.1.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 11 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, despite the stable 1.1.0 version.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long period without releases. No current development activity is visible to support compatibility fixes.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide no meaningful sign of an active user or contributor base.

Repo tooling

Composer is used for the build, which is appropriate, but no security scanning tools are configured. The absence of scanning adds a modest transparency and maintenance concern.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more for an API client that may process access tokens and application secrets.