ims/common-service

Release historydanger

The package has had no releases in nearly six years, despite 21 releases overall. Its earlier rapid release history shows past activity but does not offset the prolonged current pause.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release pause and indicating limited ongoing maintenance.

Maintainerscaution

Only one registry account has publish access, which leaves a thin publishing base. This is a supporting concern rather than proof of abandonment because registry access does not measure all project contributors.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling is reported. This is a modest hygiene gap, not evidence that the release is unsafe by itself.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. The package's README and tests improve transparency but do not replace that process.