umityatarkalkmaz/session

This release is usable and has solid baseline hygiene: it is MIT-licensed, includes a README, changelog, tests, a complete small file tree, minimal runtime dependencies, no install-time lifecycle scripts, and no detected dangerous workflow patterns. However, it is extremely new, with only two releases on the assessment date, no commits or active maintainers in the preceding three months, very limited repository adoption, and no security policy. The single-person ownership and missing explicit workflow token permissions add some transparency and operational concerns, so this is a reasonable dependency for cautious adoption but not yet a mature, strongly established one.

Latest v2.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. That is not itself a defect for an individual-owned project, but it creates limited publishing redundancy and a higher bus-factor concern.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing signal to offset the single-maintainer limitation.

Release history

The package is effectively brand new: it has only two releases and was first released on the assessment date. This leaves little evidence of sustained maintenance or long-term release reliability.

Repo commit activity

The repository records zero commits and zero active maintainers in the past three months. Because the project is newly released, this may reflect its age rather than abandonment, but it leaves sustained maintenance unproven.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is neutral for a tiny new project, but it also provides no evidence of an active user or contributor community.