Package Health/opdavies/sculpin-twig-sort-by-field-bundle

opdavies/sculpin-twig-sort-by-field-bundle

The code is tiny and has only one runtime dependency, limiting its maintenance surface. It has a valid MIT declaration and is not deprecated or archived, but the project has had no activity since 2017 and offers no security policy.

Latest 1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. Individual ownership can be normal for a small package, but it leaves little visible publishing redundancy alongside the lack of recent activity.

Project backing

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to offset the single-release history and prolonged inactivity.

Release history

This package has only one release, published over 9 years ago, with no releases in the last 12 months. That is strong evidence of abandonment, though the small package scope may reduce the need for frequent releases.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, consistent with the release history and indicating that maintenance has stopped.

Repo tooling

The repository uses Composer, which fits the package ecosystem, but has no security-scanning tooling. That is a modest transparency and maintenance gap rather than a standalone severe risk.