musoftware/driver-telegram

Release historydanger

The package has had no release in over five years, with zero releases in the last 12 months; its latest release is also its first recorded release date. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided activity signal compensates for this inactivity.

Security policycaution

The linked repository has no published security policy, leaving vulnerability reporting and response expectations less transparent for a dependency.

Workflow auditcaution

The sole workflow was fully analyzed with no dangerous audit findings or untrusted checkouts, but all three action references are unpinned. This creates avoidable build reproducibility and supply-chain hygiene risk.