jumper423/yii2-vk

The package has a clear Apache-2.0 license, a consumer-facing README, and a small, directly matching source tree. Repository security coverage is limited because no security scanning tools or security policy are present, and the project has little operational evidence beyond its basic packaging.

Latest 3.3.4

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about nine years ago, with no releases in the last 12 months. Its 23-release history shows prior activity but does not offset the prolonged current inactivity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and leaving no evidence of ongoing maintenance.

Package file tree

The package and repository contain the same six files, including README.md, LICENSE, composer.json, and the two PHP source files. The matching, compact tree provides basic publication transparency but little evidence of a broader maintenance process.

Repo issue activity

There has been no new or closed issue or pull request activity in the last month, with one issue still open. This supports the broader abandonment concern, though the small project size limits how much issue volume would be expected.

Repo tooling

Composer is used for builds, which fits the package ecosystem, but no security scanning tools are configured. That is a hygiene weakness rather than evidence that the release is unsafe.