arkitecht/firewall

Release historydanger

The latest release was in April 2019, with no releases in the last 12 months. That long release gap is strong evidence of abandonment risk for a framework integration.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this materially increases the risk that issues and framework changes will go unattended.

Project backingcaution

The repository owner is an individual account rather than an organization. That does not imply poor quality, but it indicates less visible institutional backing for a package already showing no recent activity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of an active user or contributor community.

Repo toolingcaution

Composer is used for the build, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe by itself.