Package Health

asmbs/thunderpress

Licensing and documentation are in place, and the project is not archived or deprecated. Its old WordPress stack and absent security tooling make long-term maintenance and safe upgrades difficult.

Latest v2.1.3PackagistPackagist

32%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

0

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

75

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

50

Health Score Breakdown

Release historydanger

The latest release was published over 10 years ago, with no releases in the last 12 months. Twelve releases show some historical activity, but the prolonged pause strongly raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating no visible ongoing maintenance.

Repo toolingcaution

Composer is used for builds, but no security scanning tool is configured. That is a modest transparency and maintenance gap rather than evidence of an unsafe release by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more for a WordPress stack with multiple runtime dependencies.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Kyle Tucker
James Osterhout

Direct Dependencies

DependencyLast ReleaseScore
asmbs/wp-ip
Version ^1.0
—
—
asmbs/wp-unblog
Version ^1.1
—
—
vlucas/phpdotenv
Version ^2.2
—
—
composer/installers
Version ^1.0
—
—
johnpbloch/wordpress
Version ^4.4
—
—

Weekly Downloads

Info

Last Published
10 years ago
Created
11 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform