otezz/jatis-sms

Release historydanger

The package has had only one release, published about 10 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap and leaving current maintenance capacity un demonstrated.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month, and one issue remains open. This is supporting evidence of inactivity rather than a severe risk by itself.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are configured. That leaves dependency and code-risk monitoring weaker than it could be for a maintained library.

Security policycaution

The linked repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, though it does not by itself show that the package is unsafe.