wp-content-framework/cache

Release historydanger

The package has 45 releases since March 2019, but its latest release was December 2020 and it has had no releases in nearly six years. That strongly increases abandonment risk despite its earlier regular cadence.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having been inactive since December 2020. This is a major maintenance concern.

Licensecaution

The artifact and repository contain license files, but the registry declares GPL-2.0+ while the detected artifact license is GPL-3.0. The mismatch should be resolved before adoption because it creates licensing uncertainty.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is configured. The missing scanning lowers repository hygiene, though it does not outweigh the maintenance evidence by itself.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for a dependency.