simsoft/twig

This release appears usable and reasonably transparent: it is MIT-licensed, not deprecated or archived, has a matching repository, no install-time lifecycle scripts, and the repository contains tests, a changelog, CI, and a small focused dependency set. However, maintenance evidence is mixed: the package has only three releases over roughly 887 days with one release in the last 12 months, repository commit activity shows no commits or active maintainers in the last three months, and the repository has no stars or forks. The absent security policy, absent security scanning, and workflow without declared top-level permissions are additional hygiene gaps. Overall, this is a caution-grade dependency whose adoption is plausible but should account for its very small maintainer and activity footprint.

Latest 3.0.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a limited publishing base for a user-owned project and increases continuity risk, although registry access alone does not establish actual maintenance activity.

Project backing

The repository is owned by a user account rather than an organization, so there is no organizational backing signal to offset the thin maintainer and activity profile.

Release history

The package is about 887 days old but has only three releases, with one release in the last 12 months and a median interval of about 392 days; this indicates a slow release cadence and warrants caution about responsiveness.

Repo commit activity

No commits and no active maintainers were observed in the last three months. Combined with the slow release cadence, this is meaningful evidence of limited current maintenance capacity.

Repo popularity

The repository has zero stars and forks and only two watchers. Popularity is not decisive, but this provides little supporting evidence of a broad or durable community.