php-collective/toml

Clear documentation, a matching repository, and a small runtime dependency set reduce adoption friction. The young 0.1 release line, nearly four months without commits, and unpinned workflow actions leave meaningful maintenance and build-reproducibility concerns.

Latest 0.1.5

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months, which is a meaningful warning for a package that is still in its 0.1 development line.

Repo issue activity

One issue and one pull request remain open, with no issues or pull requests closed in the last month; this modestly reinforces the signs of slowed activity.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap rather than evidence of abandonment.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.

Version stability

Version 0.1.5 is not yet on a stable major version, so its API and compatibility expectations may still change despite it not being marked prerelease.