pantheon-systems/example-wordpress-composer

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. This is a direct indication that new projects should not depend on it.

Release historydanger

The latest registry release was published about two and a half years ago, and there were no releases in the last 12 months. That lack of distribution activity materially increases the risk of depending on an obsolete template.

Repo commit activitydanger

The repository had zero commits and zero active maintainers during the last three months. This confirms that there is no recent development activity to offset the abandonment signals.

Repository archiveddanger

The linked source repository is archived, which is a severe abandonment signal even though it was pushed recently. Archived projects generally should not be expected to receive ongoing maintenance.

Project backingcaution

The repository is owned by an organization and is clearly tied to the package namespace, which provides stronger ownership context than an unbacked project. That positive context is outweighed by the deprecated organization and archived repository state.