lion/spreadsheet

This release appears generally healthy and suitable for consideration: it has a stable v6.1.5 release, 30 releases over more than three years, 10 releases in the last 12 months, a recent repository push, tests and a changelog, a clear MIT license, minimal runtime dependencies, and no deprecation or install-time lifecycle scripts. The main concerns are that recent repository activity is limited to one commit from one contributor, the repository has very little visible popularity, no security policy, and incomplete top-level GitHub Actions permission declarations. These issues warrant monitoring and review before adoption, but they do not indicate abandonment because release activity and repository maintenance remain current, and the project is organization-backed.

Latest v6.1.5

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, which is a mild publishing continuity concern, although the organization-owned repository provides some backing context.

Repo bus factor

All one recent commit came from a single contributor, creating a concentrated short-term bus factor. Organization backing partially mitigates handoff risk but does not remove the observed concentration.

Repo commit activity

There was one commit in the last three months, showing recent activity but a low maintenance cadence compared with the package's recent release frequency.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little external validation.

Security policy

No repository security policy was found, leaving vulnerability-reporting guidance less transparent than ideal.