Package Health

tomasvotruba/class-leak

This release appears healthy and suitable for dependency use: it is actively released, currently maintained, not deprecated or archived, has a stable major version, a matching repository with substantial source and test coverage, and no install-time lifecycle scripts or dangerous workflow patterns. The main risks are concentrated ownership, with all 15 commits in the last 3 months made by one maintainer, and limited security-process maturity because no security scanning or security policy was detected and workflow token permissions are not explicitly restricted. These concerns warrant monitoring but do not outweigh the package's strong release and repository evidence.

Latest 2.2.4PackagistPackagist

82%

Total Score

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

63

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

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

94

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational handoff buffer to offset the concentrated maintainer activity. The individual owner is nevertheless demonstrably active through recent commits and releases.

Repo bus factorcaution

One contributor made 100% of the last 3 months' commits, creating a genuine single-maintainer continuity risk. The active release cadence and recent repository activity partly mitigate abandonment concerns but do not remove the bus-factor weakness.

Repo commit activitycaution

The repository received 15 commits in the last 3 months, showing current activity. However, all activity came from one maintainer, so the maintenance evidence is tempered by concentration risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a security-process gap, though it is not by itself evidence that the package is unsafe or unmaintained.

Security policycaution

No repository security policy was found. This reduces vulnerability-reporting transparency, but it is a process gap rather than evidence of abandonment.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
nette/utils
Version ^4.1
symfony/finder
Version ^7.4|^8.0
entropy/entropy
Version ^0.4.6
nikic/php-parser
Version ^5.7
webmozart/assert
Version ^2.0

Weekly Downloads

Info

Last Published
18 days ago
Created
3 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