pfefferle/wordpress-humanstxt

Release historydanger

The package has had only two releases, with the latest published in March 2017 and none in the last 12 months. This is strong evidence of a long-standing maintenance gap, although the package may be stable and narrowly scoped.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the package's extended release inactivity. The repository is not archived, but there is no observed recent development activity.

Project backingcaution

The package and repository are owned by the same individual account, so there is no organizational backing signal to offset the thin maintenance history. This is context for the inactivity, not a problem by itself.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling is reported. The missing scanner is a modest transparency gap rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. For this small package this is a limited concern, but it weakens maintenance transparency.