mmmcatoo/object_mapper

Release historydanger

The package is about 4 years and 8 months old, but all 4 releases occurred within roughly 53 minutes and none appeared in the last 12 months. This strongly suggests the project has been inactive since its initial release burst.

Maintainerscaution

One registry account has publish access. Because the repository is owned by the same individual rather than an organization, the single-maintainer base adds resilience risk if that person stops maintaining the project.

Package scaffoldingcaution

The artifact contains no README, tests, or changelog, while the linked repository also reports none. Missing tests and changelog are normal packaging gaps, but the absent README reduces consumer transparency for a library.

Project backingcaution

The registry namespace and repository owner are the same individual account, with no organization backing shown. That is consistent ownership, but it leaves the project dependent on a single maintainer.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull-request activity. While this avoids an unresolved backlog, it provides no evidence of ongoing maintenance or community engagement.