tormjens/wp-blade

The six-file package is easy to inspect and has a clear README, while its two runtime dependencies keep integration relatively simple. Current compatibility is unverified, and the repository provides no security policy or scanning evidence.

Latest 2.0.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in August 2016, nearly 10 years ago, with no releases in the last 12 months. The seven-release history shows an established package, but not current maintenance.

Repo commit activity

The repository has had zero commits and zero active maintainers in the last three months, while its last push was in October 2018. This strongly increases abandonment and compatibility risk.

Repo issue activity

There has been no issue or pull-request activity in the last month, with one issue still open. This is consistent with the long maintenance gap and provides no evidence of active support.

Repo tooling

Composer is used for builds, but no security scanning tools are present. For a package that has not been maintained for years, the lack of automated security checks adds a transparency gap.

Security policy

The linked repository has no security policy. This is a secondary transparency weakness, especially alongside the absence of recent maintenance, though it is not evidence of a vulnerability by itself.