xethron/bignum

The package is clearly licensed, tested, documented, and has no install-time scripts. Its single-user ownership, absent security policy, and unpinned workflow actions leave limited maintenance and build-transparency margin.

Latest v0.2.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months. Combined with the old latest release, this is meaningful evidence of stopped maintenance.

Project backing

The repository owner is an individual user rather than an organization, so there is no observed organizational backing to compensate for the package's single-maintainer structure.

Release history

Only 3 releases have been published since October 2018, with no releases in the last 12 months and a median interval of about 876 days. This indicates a slow, currently inactive release cadence.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe defect for this small library.

Security policy

The repository has no security policy. That leaves vulnerability reporting and response expectations unclear, especially for a package with no recent activity.