flow/bitwiser

Release historydanger

The latest of only three releases was published in June 2014, and there have been no releases in over 12 years. This is strong evidence that maintenance has stopped.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last push. The non-archived status does not compensate for the absence of activity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month and no open work. While a small stable project can have little issue traffic, this adds to the evidence of abandonment here.

Repo popularitycaution

The repository has 3 stars and no forks, indicating a small adoption footprint. Low popularity is supporting context, not a standalone health failure, but it offers little external maintenance evidence.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a hygiene gap rather than a standalone dependency blocker.