limur/map

Release historydanger

The package has had no release in more than six years, despite five releases clustered in April 2020. This is strong evidence of abandonment risk for a framework bundle.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the long release gap and providing no evidence of current maintenance.

Repo package mentioncaution

The linked repository name does not match the package name, and no README mention was observed. That makes package-to-source ownership less transparent, although a subpackage or renamed repository could explain it.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, not evidence of malicious behavior.