dnaber/requisite

Release historydanger

Only two releases were published, both in March 2016, with no releases in the last 12 months. This is a substantial maintenance and compatibility concern for a library dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months. Together with the old release history, this points to limited ongoing maintenance capacity.

Repo issue activitycaution

Three issues remain open, with no new or closed issues and no pull-request activity in the last month, suggesting limited current project engagement.

Repo popularitycaution

The repository has only 3 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad maintenance community.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools were detected, leaving a modest repository-hygiene gap.