Package Health

bnussbau/epaper-pipeline-php

The release history, documentation, tests, and security policy provide a solid foundation. Maintenance is concentrated in one contributor, while workflow permissions, unpinned actions, and a high-confidence bot-condition warning add ongoing upkeep risk.

Latest 1.1.0PackagistPackagist

72%

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

100

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

83

Health Score Breakdown

Project backingcaution

The package and repository are owned by the same individual account, so the single-contributor concern is not offset by organization backing.

Repo bus factorcaution

One contributor made all recent commits, concentrating maintenance and review capacity in a single person.

Repo commit activitycaution

Only two commits were made in the last three months, so recent development activity is limited despite the strong release cadence.

Workflow auditcaution

All four workflows were analyzed, but all nine action references are unpinned, three workflows grant top-level write permissions, and a high-confidence bot-conditions finding affects the Dependabot auto-merge workflow. A low-confidence-free adhoc-packages finding also shows a test workflow installs outside a lockfile.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

bnussbau

Direct Dependencies

DependencyLast ReleaseScore
league/pipeline
Version ^1.0
—
—
spatie/browsershot
Version ^5.0
—
—

Weekly Downloads

Info

Last Published
2 months ago
Created
1 year 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