pinga/http

Clear documentation, tests, and a minimal dependency footprint reduce adoption friction. The missing security policy and scanning leave less evidence for handling future issues.

Latest v0.1

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the package's only release, published about three years and seven months ago, with no releases in the last 12 months. That strongly raises abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months. Combined with the single old release, this is strong evidence of inactive maintenance.

Repo popularity

The repository has zero stars and one fork. Popularity is only supporting evidence, but these very limited adoption signals provide little reassurance for a package that has no recent activity.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. The missing scanning reduces supply-chain and maintenance assurance.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself make the package unfit.