ppranav/table-insights

Release historydanger

Only four releases were published, with none in the last 12 months; the latest release was about three years and seven months ago. This strongly raises abandonment risk, despite the package having a short initial release interval.

Maintainerscaution

One registry account publishes the package, leaving little visible maintainer redundancy if that person stops responding. The linked project is user-owned rather than organization-backed, so the narrow base matters more.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last push. The repository is not archived, but there is no observed recent development to offset the inactivity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not required for a healthy package, but these numbers provide no supporting evidence of a broader user or contributor community.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and assurance gap, not evidence that the release is unsafe by itself.