buku-masjid/demo-data

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the strongest evidence that fixes may not arrive promptly.

Release historycaution

The latest release was over two years ago, and there were no releases in the last 12 months. This materially raises maintenance and abandonment concerns despite the package having three releases overall.

Repo issue activitycaution

There is one open issue and one open pull request, but none were opened or closed in the last month, offering no evidence of current issue or review activity.

Repo popularitycaution

The repository has one star and five forks, indicating a small user base. Popularity is only supporting evidence, so this lowers confidence in external scrutiny without making the package unsafe to use by itself.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a transparency gap, although it is less significant than the demonstrated maintenance inactivity.