Package Health

mreschke/helpers

The stable MIT-licensed release has a clear, small source tree and no install-time scripts. Maintenance appears stopped, and the single-person project has no security policy.

Latest 5.3.0PackagistPackagist

42%

Total Score

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

25

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

67

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

88

Health Score Breakdown

Release historydanger

The package has had no release in more than three years and none in the last 12 months, despite nine releases overall. Its earlier release cadence shows prior activity but does not offset the prolonged gap.

Repo commit activitydanger

There were no commits and no active maintainers in the measured three-month period, consistent with maintenance having stopped for a prolonged period.

Maintainerscaution

Only one registry publishing maintainer is listed. Individual ownership is not inherently unhealthy, but it leaves limited visible publishing redundancy alongside the inactive project.

Repo package mentioncaution

The repository name matches the package, but its README does not mention the package name directly. That creates a modest ownership and packaging-transparency concern.

Repo toolingcaution

Composer is used for the build, providing expected ecosystem tooling, but no security scanning tools were detected. The missing scanner is a modest transparency gap rather than proof of unsafe code.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Matthew Reschke

Direct Dependencies

No direct dependencies.

Weekly Downloads

Info

Last Published
3 years ago
Created
8 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