musoftware/botman-viber-driver

Release historydanger

The package has made no releases in nearly six years, with only three releases overall; this is strong evidence of abandonment for a dependency that must track its ecosystem.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and materially increasing maintenance risk.

Repo issue activitycaution

There were no new or merged pull requests and no issue activity in the last month, so there is no recent evidence of support or defect handling.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this is a modest transparency gap, especially for an inactive project.

Workflow auditcaution

The single workflow was fully audited with no findings, no untrusted checkouts, and no script injection; both action references are unpinned, a minor reproducibility and supply-chain hygiene gap.