orkhanahmadov/sipgate

Release historydanger

Only two releases were published, with the latest about seven years ago and none in the last 12 months. That long gap is a meaningful abandonment concern for a library dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old latest release, this indicates that maintenance has effectively stopped.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence of malicious behavior.

Repository archivedcaution

The repository is not archived, but its last push was about six years ago, which is consistent with the broader evidence of stale maintenance.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.