kunicmarko/graphql-test

Release historydanger

The package has only two releases, with the latest published about six years ago and no releases in the last 12 months. This strongly suggests maintenance has stopped, despite the release having documented notes.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No newer activity is provided to offset the abandonment risk.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, with one issue still open. This is a small caution because it provides no evidence of active support.

Repo toolingcaution

The project uses Composer and Make, but no security-scanning tools are present. Build tooling is a positive foundation, while the missing security checks add a modest maintenance concern.

Security policycaution

The repository has no security policy. That does not show a vulnerability, but it reduces transparency about how security reports would be handled for a dependency with no recent maintenance activity.