Package Health/fostercommerce/craft-config

fostercommerce/craft-config

This is a usable but very new release with several positive hygiene indicators: it has an MIT license and license file, a substantial README, a matching source repository owned by an organization, no deprecation status, no install-time lifecycle scripts, and a cleanly analyzed workflow with no dangerous patterns. However, the package is only 0 days old with one release, one commit from one active contributor, no tests or changelog, no security policy, and workflow token permissions are not explicitly constrained. The organization backing is reassuring, but the limited observed maintenance history means adopters should treat it as a developing dependency and verify its stability for their use case.

Latest 1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact and repository include a substantial 9,542-character README, but neither includes tests or a changelog; for a newly released configuration wrapper, this leaves maintenance and change-history coverage limited.

Release history

This is the first and only release, published 0 days ago, so there is no observed release track or history demonstrating sustained maintenance.

Repo bus factor

All one recent commit came from a single contributor, creating a concentrated observed maintenance base. Organization ownership provides some handoff potential, but no second active contributor is shown.

Repo commit activity

Only one commit was recorded in the last three months from one active maintainer. For a package released 0 days ago this is consistent with its early stage, but it does not yet demonstrate sustained maintenance.

Repo tooling

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