jlis/judge

Release historydanger

The package has had no release in about nine years, with five releases all concentrated on 8 May 2017. That long gap materially raises abandonment and compatibility risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly nine-year release gap and providing no evidence of current maintenance.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while four issues remain open. This supports the conclusion that the project is inactive rather than actively maintained.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 2 watchers. Popularity is not decisive by itself, but it provides little supporting evidence of a broad maintenance community.

Repo toolingcaution

The repository uses Composer for builds, but no security scanning tools were detected. The build tooling is appropriate, while the missing scanning is a minor hygiene gap.