lbinf/alisms

Release historydanger

The package has had no release in more than nine years: its latest release was in March 2017, despite nine total releases. This is strong evidence of abandonment for a dependency that may need updates.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in March 2017. No newer maintenance activity compensates for this gap.

Repo popularitycaution

The repository has one star and no forks, providing little evidence of community review or backup maintainers. Popularity is supporting evidence rather than decisive on its own.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security-scanning tools are configured. That leaves dependency and repository security checks undocumented.

Security policycaution

The linked repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This matters more for an SMS client that handles service credentials and requests.