gizburdt/scaffolder

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. This is a severe dependency-maintenance risk and outweighs the package's stable version status.

Release historydanger

The package has 36 releases since April 2015, but none in the last 12 months; its latest release was in August 2019. The long period without a release indicates likely abandonment.

Dependency profilecaution

The package has five declared runtime dependencies, including its framework and theme-support components. This is a moderate dependency surface rather than an inherently unhealthy one, but the absence of recent releases means compatibility updates may not be available.

Maintainerscaution

Only one registry account has publish access. This does not prove who actively maintains the project, but combined with the lack of recent releases it provides little evidence of ongoing maintenance capacity.

Package scaffoldingcaution

The published artifact has no README, which is a meaningful consumer-ergonomics and transparency gap for a framework intended to support WordPress themes. The absence of tests and a changelog in the artifact is normal packaging practice and is not a concern here.