ipiner/upload

Clear documentation and a tested source tree help with adoption. The project is only 42 days old, with one commit from one contributor in the last three months; security scanning and a security policy are also absent.

Latest v1.0.1

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the concentrated maintainer activity is not offset by visible organizational backing.

Release history

The package is only 42 days old and has two releases, with a 42-day median interval. This is limited evidence of long-term maintenance, though the latest release was published recently.

Repo bus factor

One contributor made 100% of the recent commits. This concentrates maintenance knowledge and creates a meaningful continuity risk for a young package.

Repo commit activity

Only one commit and one active maintainer were observed in the last three months. The recent push is positive, but the activity base is too thin to demonstrate durable maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a transparency and hygiene gap rather than evidence that the package is unsafe.