amprest/dt-tables

A single runtime dependency keeps integration straightforward, and the repository clearly matches the package under organizational ownership. Recent commit activity is absent despite a current release, while consumer documentation and a security policy are missing.

Latest v2.06

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The published package has no README, which is a real consumer-documentation gap for a Laravel data-table component. Missing tests and changelog files are normal for a published artifact and do not add concern here.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Although the repository was pushed recently and the registry has a current release, the lack of observed development activity is a meaningful maintenance concern.

Repo popularity

The repository has zero stars and forks and only two watchers, indicating little visible community adoption. Popularity is supporting evidence rather than a verdict, so this modestly lowers confidence in long-term support.

Repo tooling

Composer is used as a build tool, which fits the package ecosystem, but no security-scanning tooling is present. This is a hygiene gap rather than evidence that the release is unsafe.

Security policy

The repository has no security policy. For a Laravel package that can affect application data and routes, the absence of a documented vulnerability-reporting path reduces transparency.