gap-db/orm-cache

Release historydanger

The latest release was published in June 2016, and there were no releases in the following 10 years. This is strong evidence of abandonment for a dependency that may need fixes or compatibility updates.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and leaving little evidence of current maintenance capacity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month; open counts are unknown, so this supports limited activity without proving that all support work has stopped.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the repository may not clearly establish ownership of this release. The organization backing partly offsets that concern but does not remove it.

Repo popularitycaution

The repository has 0 stars and 0 forks, with 2 watchers. Popularity is only supporting evidence, but these counters offer little additional confidence in project maturity or community support.