atk14/core

The package includes its license, README, and changelog, with no install-time scripts or excessive runtime dependencies. The single recent commit and absent security policy leave maintenance and security processes thin despite organization backing and an unarchived repository.

Latest v1.7

Packagist

57%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one registry release, nearly five years ago, with no releases in the last 12 months. Recent repository activity partly offsets the age of the published release but does not establish a reliable release cadence.

Repo bus factor

All one recent commit came from a single contributor, creating a concentrated operational dependency. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo commit activity

The repository has only one commit in the last three months, showing some current activity but a very sparse maintenance pace. That weakens confidence that fixes and releases will arrive consistently.

Repo tooling

Composer build tooling is present, but no security scanning tooling was detected. This is a process gap rather than evidence of an unsafe release.

Security policy

The repository has no security policy, so there is no documented reporting or response process for vulnerabilities. The gap affects transparency but is not a severe risk by itself.