stanleymsacommon/msacommon

Release historydanger

The package has had no release in more than seven years: all 10 releases were published by August 2019, with none in the last 12 months. This is strong evidence of abandonment for a library dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with a project that has not been maintained since 2019.

Maintainerscaution

The registry lists one maintainer. A single maintainer increases continuity risk here because the repository also shows no recent commits or active maintainers.

Package scaffoldingcaution

A changelog and consumer-facing README are present; the absence of packaged tests is normal and not a health gap. However, the README content is largely a template, limiting consumer transparency.

Project backingcaution

The repository owner is an individual user rather than an organization, and the available evidence shows no broader project backing. Combined with one registry maintainer and no recent activity, this increases continuity risk.