abr4xas/mcp-tools

The project has a clear MIT license, documented releases, repository tests, and recent publication activity. Maintenance is uncertain because there were no commits in three months, while workflow permissions and the high-confidence bot-condition finding add avoidable release-process risk.

Latest v2.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

100

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package runs a post-autoload-dump install-time script. This is worth awareness during installation, but the signal does not by itself show unsafe behavior or poor maintenance.

Maintainers

Only one registry account has publish access. The repository is user-owned rather than organization-backed, so this represents a thin publishing base and limited continuity if that maintainer becomes unavailable.

Project backing

The package and repository are both owned by the same individual account, which supports provenance but offers no organizational backing to offset the single-maintainer risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. That is a meaningful maintenance concern for a package released only recently.

Security policy

The repository has no security policy. This is a transparency gap for a package that analyzes application routes and integrates with an MCP server, though it is not by itself a release blocker.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Angel

Direct Dependencies

Dependency	Last Release	Score
laravel/mcp Version ^0.5.1	—	—
nikic/php-parser Version ^5.7	—	—
illuminate/contracts Version ^11.0\|\|^12.0	—	—
spatie/laravel-package-tools Version ^1.16	—	—