pachel/tableadmin

Its two runtime dependencies and absence of install-time scripts keep the integration surface modest. The source repository is not archived, but it has no security scanning or security policy and shows no commits from maintainers in the last three months.

Latest 2.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

The package declares no license, contains no license file, and the repository also has no detected license file. That creates a real adoption and redistribution risk for an open-source dependency.

Package scaffolding

A README is present and the package has a GitHub release, but the README contains no text. Tests and changelog files are not expected in the published artifact, so their absence is not penalized.

Release history

The package is about 2 years and 9 months old with six releases and two releases in the last 12 months. The latest release is current, but the small history and clustered release timing provide limited evidence of sustained maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Although the current release and repository push show recent publication activity, ongoing maintenance capacity is not demonstrated.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. This is a modest transparency and maintenance gap rather than a severe risk.