craftcms/gatsby-helper

MIT licensing, a matching repository, and organizational ownership improve transparency. The small dependency surface, release notes, security policy, and clean workflow audit provide useful safeguards, though action references are not pinned.

Latest 2.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 22 releases over about 6 years, but its latest registry release was about 2 years and 6 months ago and it had no releases in the last 12 months. This is a meaningful maintenance concern despite its previously regular median release interval of about 28 days.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. This reinforces the long gap since the latest package release and raises abandonment concern.

Repo issue activity

There were three open issues and three open pull requests, but no new or closed issues or pull requests in the last month. This suggests limited recent project interaction.

Repo tooling

The repository uses Composer for builds, but no security scanning tools were detected. The missing scanning is a hygiene gap, while the build tooling itself is appropriate.

Workflow audit

All 3 workflows were analyzed with no reported audit findings, no untrusted checkouts, and no script injection. However, all 3 of 3 action references are unpinned, which leaves build inputs less reproducible.