Package Health/sashabo/self-signed-certs

sashabo/self-signed-certs

The small, single-owner project has no security policy or security scanning, which limits confidence in ongoing maintenance. Its clear README, minimal dependencies, license, and matching repository make adoption practical despite the aging release.

Latest 1.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only one release exists, published nearly three years ago, with no releases in the last 12 months. This is meaningful evidence of limited ongoing maintenance, although a small stable library may need few releases.

Repo commit activity

There were no commits and no active maintainers in the last three months. Together with the old latest release, this leaves little evidence of current maintenance capacity.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. For a library that creates certificates and handles key material, this is a modest transparency and maintenance gap.

Repository archived

The repository is not archived, but it was last pushed nearly three years ago. That avoids an abandonment verdict while still indicating stale source activity.

Security policy

The repository has no security policy. That makes vulnerability reporting and response expectations unclear, though it is not by itself evidence that the package is unsafe.