dazet/data-map

The release has clear documentation, release notes, tests in the repository, and a permissive MIT license. Its long release gap and absent recent commit activity make future fixes and support uncertain.

Latest v0.2.0

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases and none in the last 12 months; the latest release was nearly seven years ago. This is substantial abandonment risk despite the repository remaining available.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this points to inactive maintenance.

Repo issue activity

There were no newly opened or closed issues or pull requests in the last month, with one issue and one pull request still open. This provides little evidence of ongoing support.

Repo tooling

Composer build tooling is present, but no security scanning tooling was detected. The missing scanner is a hygiene gap, not evidence that the release is unsafe by itself.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap for a maintained library, though it is less severe than the inactive development signals.