fawno/modbus

Release historydanger

The latest release was over four years ago, with no releases in the last 12 months. That indicates substantial abandonment risk despite 13 releases overall.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the long release gap and limited ongoing maintenance.

Maintainerscaution

Only one registry account can publish releases, which creates a thin operational base. Organization backing partly offsets this concern, but does not demonstrate active maintenance.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence of unsafe code.

Security policycaution

The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This matters more for a protocol library but is secondary to the maintenance risk.