bitbag/graphql-plugin

Release historydanger

The latest release was about three years ago, with no releases in the last 12 months, despite a previously regular release cadence. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers during the last three months, reinforcing the stale release history.

Lifecycle scriptscaution

The package runs post-create, post-install, and post-update scripts, which increases installation complexity and the amount of package code executed during dependency operations.

Repo package mentioncaution

The linked repository name does not match the package name and its README does not mention the package, so package ownership is not transparent even though the repository is organization-owned.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The organization backing provides some context but does not replace a reporting process.