pwf0112/https

The project is a very small, single-maintainer wrapper with no security policy or scanning, so future fixes and transparency are limited. Its MIT declaration, focused dependency set, clean package contents, and non-deprecated status provide some reassurance.

Latest v1.0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was nearly 10 years ago, with only two releases overall and none in the last 12 months. This is strong evidence of abandonment risk for a package developers may need to maintain over time.

Repo commit activity

There were no commits and no active maintainers in the last three months, with the repository last pushed nearly 10 years ago. This is direct evidence that fixes and review are unlikely to be ongoing.

Maintainers

Only one registry maintainer is listed, which limits publishing continuity. The linked project is user-owned rather than organization-backed, so there is no provided backing signal to compensate for that thin base.

Project backing

The registry namespace and repository owner match, and the owner is an individual user. This supports repository identity but provides no organizational continuity.

Repo popularity

The repository has zero stars and forks and only one watcher, providing no meaningful community support or adoption evidence. Popularity is supporting evidence, but this reinforces the lack of maintenance signals.