Package Health/kanekescom/bkn-api-gateway

kanekescom/bkn-api-gateway

Usable with caveats: it has clear documentation, tests, an MIT license, and an organization-backed repository, but the project is young and has had no commits or active maintainers for about four months. The absence of a security policy and security scanning also limits maintenance transparency.

Latest v1.0.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package defines a post-root-package-install script. Install-time execution adds some operational review burden, although this is a common Composer pattern and is not severe on its own.

Release history

This is a young package, about 5 months old, with only two releases and roughly 27 days between them. That is limited maturity evidence, though the release cadence is not inherently alarming.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, indicating that maintenance has currently stalled on a young project.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is not evidence of health by itself, but it provides no sign of active community maintenance.

Repo tooling

The repository uses Composer, showing basic build tooling, but it has no security-scanning tools. For a server-side API gateway, that is a meaningful transparency and maintenance gap.