fawno/metadata-toolkit

This release is usable but carries meaningful maintenance uncertainty. It has a clear MIT license, a substantial 321-file source tree, tests in both the artifact and repository, matching repository identity, read-only workflow permissions, no install-time scripts, and an active recent release history of 16 releases over about 10 months. However, it remains pre-1.0, the repository reports no commits or active maintainers in the last 3 months, has no security policy or security-scanning tooling, and has no changelog. The organization-owned repository and recent publication activity partially offset the thin observed development activity, but the package should be adopted with monitoring rather than treated as a mature dependency.

Latest 0.0.17

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry publishing account is listed, which is a limited publishing-bus-factor concern; the organization-owned repository provides some compensating project backing.

Repo commit activity

The repository records zero commits and zero active maintainers over the last 3 months, a significant maintenance warning despite the recent release and push timestamps.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is not inherently negative, but it provides no evidence of an active user or maintainer feedback loop.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this lowers external validation modestly rather than determining the verdict.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured, leaving a security-hygiene gap.