Package Health/async-aws/dynamo-db-session

async-aws/dynamo-db-session

This is a generally healthy and usable dependency: it has a stable MIT-licensed release, a release history spanning more than six years, a current release and repository push, no registry deprecation, a matching repository with tests and CI scaffolding, and no install-time lifecycle scripts. The main concerns are limited recent activity, complete concentration of the last three months’ commits in one contributor, very low repository popularity, and the absence of a security policy and explicit workflow token permissions. Organization ownership and repository tests partially mitigate the contributor and artifact-hygiene concerns, but the package still warrants ordinary maintenance and security review before adoption.

Latest 1.3.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

All 2 recent commits came from one contributor, creating a concentrated maintenance risk. The organization-owned repository provides some capacity to hand off maintenance, so this is caution rather than severe risk.

Repo commit activity

There were 2 commits in the last 3 months, showing recent activity but at a low pace.

Repo issue activity

There were no new or closed issues or pull requests in the last month, leaving limited evidence of community or maintenance interaction; the null issue totals are unknown rather than negative.

Repo popularity

The repository has only 3 stars and 0 forks, so external adoption and community validation are limited; this is supporting caution rather than a decisive health failure.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a security-hygiene gap.