metarush/data-mapper

Repo commit activitycaution

There were zero commits and zero active maintainers in the last three months. The recent release offsets this somewhat, but the lack of current source activity raises maintenance risk.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 1 watcher, so there is little public adoption evidence or external review capacity. Low popularity is supporting caution rather than proof of poor maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. For a library handling database access, that is a transparency and maintenance gap, though it is not severe alone.

Security policycaution

The repository has no security policy, leaving no documented route for reporting vulnerabilities or communicating remediation. This is a genuine transparency gap, but it does not indicate that the package is unsafe by itself.