Package Health/takielias/tablar-crud-generator

takielias/tablar-crud-generator

This release appears suitable to depend on: it is an established, stable-major package with 18 releases over roughly 3.9 years, seven releases in the last 12 months, a recent release, a non-archived matching repository, tests, an MIT license, and no install-time lifecycle scripts. The main concerns are that commit activity reports no commits or active maintainers in the last three months despite recent release and pull-request activity, the project is maintained by a single user account, and no security policy or automated security scanning was observed. These issues reduce transparency and resilience but do not outweigh the strong release, repository, testing, and licensing evidence.

Latest 3.3.2

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, creating some continuity and bus-factor concern; however, this is a user-owned project and registry access does not by itself measure actual maintenance activity.

Project backing

The repository is owned by a user account rather than an organization, so there is no organizational backing signal to offset the single-publisher continuity concern.

Repo commit activity

No commits and no active maintainers were recorded in the last three months, which is a meaningful maintenance concern; recent releases, a recent push, and four merged pull requests provide partial evidence that development has not stopped entirely.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a security-hygiene gap that does not by itself indicate unsafe code.

Security policy

The repository has no security policy, reducing the transparency of vulnerability reporting and response expectations.