stolt/llms-txt-php

This release appears healthy and suitable to depend on: it is actively released, stable, non-deprecated, licensed, backed by a matching repository, and supported by recent commit activity, tests, changelog, and GitHub releases. The main reservations are that recent commits are highly concentrated in one of two contributors, the repository has no security policy or configured security-scanning tool, and its workflows do not declare top-level token permissions. These are meaningful hygiene and continuity concerns, but they do not outweigh the package's active maintenance and otherwise coherent publication structure.

Latest v4.3.0

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. Because the repository is user-owned rather than organization-owned, this is a modest publishing continuity concern, though active repository work provides some compensation.

Project backing

The source repository is owned by the user account raphaelstolt rather than an organization, so there is no organizational maintenance-backup evidence. Active commits and releases partially compensate for that limitation.

Repo bus factor

One contributor made 25 of 26 commits, or about 96%, in the last three months. A second contributor remains active, but the extreme concentration creates a genuine continuity risk for this user-owned project.

Repo tooling

Composer build tooling is present, but no security-scanning tool is configured. The missing security automation is a hygiene gap, not evidence of abandonment or maliciousness.

Security policy

The repository has no security policy. This reduces vulnerability-reporting transparency, but it is a moderate hygiene gap rather than a standalone dependency-blocking risk.