Package Health

takielias/tablar-kit

This release appears usable and generally well-maintained: it has a valid MIT license, a substantial repository with tests and a changelog, 60 releases over roughly 979 days, 17 releases in the last 12 months, a stable non-prerelease version, an active non-archived repository, and no registry deprecation. The main concern is that the repository recorded zero commits and zero active maintainers in the last three months, despite recent release and pull-request activity, which makes current maintenance capacity less clear. A single registry maintainer, absent security policy, and incomplete GitHub Actions permission declarations add moderate transparency and governance concerns, but no severe abandonment signal is present.

Latest 13.6.1PackagistPackagist

72%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

63

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

94

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Maintainerscaution

Only one account has registry publish access, which creates a bus-factor concern for release administration. This is partly offset by the linked repository and sustained release history, but no organization backing is shown.

Project backingcaution

The repository is owned by the individual account takielias rather than an organization. This is valid project backing, but it offers less institutional continuity than organization ownership and reinforces the single-maintainer concern.

Repo commit activitycaution

The repository reports 0 commits and 0 active maintainers in the last three months, despite a release and recent merged pull requests. This discrepancy weakens confidence in current development continuity and raises a maintenance concern.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tool is detected. The missing scanner is a governance gap rather than evidence of an unsafe release, and other workflow signals are clean.

Security policycaution

The repository has no security policy. This reduces transparency around vulnerability reporting and response expectations, though it is not by itself evidence of abandonment.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Taki Elias

Direct Dependencies

DependencyLast ReleaseScore
nesbot/carbon
Version ^3.0
—
—
takielias/lab
Version ^1.1
—
—
illuminate/view
Version ^12.0|^13.0
—
—
takielias/tablar
Version ^13.5
—
—
illuminate/support
Version ^12.0|^13.0
—
—

Weekly Downloads

Info

Last Published
20 days ago
Created
2 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform