sscs/opensearch

Release historydanger

The package has only one release, published about 9 years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk despite the stable version label.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, and its last push was about 9 years ago. The lack of recent maintenance materially increases the risk of unaddressed compatibility issues.

Repo popularitycaution

The repository has 0 stars, 0 forks, and 1 watcher. Popularity is only supporting evidence, but these values provide no community signal to compensate for the long maintenance gap.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. That leaves a modest quality and supply-chain hygiene gap without outweighing the maintenance evidence.

Security policycaution

No security policy is present. This is a transparency and response-process gap, although it is less severe than the package's prolonged inactivity.