seffeng/signature

Tests, a README, and a small dependency surface improve day-to-day adoption. The repository is current and correctly linked, but it lacks a security policy and automated security scanning.

Latest v0.1.8

Packagist

66%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 6 years but has only 9 releases, with one release in the last 12 months and a typical interval of about 7.5 months. The recent release shows continued activity, but the cadence is slow.

Repo bus factor

All recent commits came from one contributor, leaving little demonstrated redundancy if that maintainer becomes unavailable. The linked repository is active, but no second active contributor compensates for this concentration.

Repo commit activity

The repository had one commit in the last 3 months, which is some evidence of current maintenance but indicates limited recent development activity.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. That is a modest transparency and maintenance gap rather than evidence of a security defect.

Security policy

The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.