comsave/soap-client

Release historydanger

The latest release was over six years ago, with no releases in the last 12 months. This strongly raises abandonment and compatibility risk despite a history of 17 releases.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with more than six years since the last release. This is strong evidence of likely abandonment.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe by itself.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This adds a smaller transparency concern alongside the much more significant inactivity.

Version stabilitycaution

Version 0.2.2 is not a prerelease, but the project remains below 1.0, which provides less evidence of mature API stability. The long period without releases reinforces that concern.