32d/wordpress-project

The package has a usable README, a clear Composer-based layout, and an MIT declaration backed by organizational ownership. It lacks a security policy and shows no recent issue or repository activity, leaving maintenance responsibility concentrated in a project with little visible adoption.

Latest 1.1.2

Packagist

46%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is about 773 days old, has had five releases, and has had no release in the last 12 months; the rapid initial releases do not compensate for the long subsequent pause.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, which is strong evidence that maintenance has stopped or become difficult to verify.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no external sign of active use or review.

Repo tooling

The project uses Composer for its build and dependency workflow, which fits the package's stated purpose; no security scanning tool is present, leaving a modest hygiene gap.

Security policy

The linked repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a package that manages a WordPress application setup.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Lily Bergonzat

Direct Dependencies

Dependency	Last Release	Score
laravel/helpers Version ^1.5	—	—
vlucas/phpdotenv Version ^5.4	—	—
illuminate/support Version ^8.83	—	—
johnpbloch/wp-cli-phar Version ^2.6	—	—
johnpbloch/wordpress-core Version @stable	—	—