openl10n/sdk

Release historydanger

Only two releases exist, with none in the last 12 months; the latest release was in November 2015, more than 10 years ago. This strongly raises abandonment risk.

Repo commit activitydanger

There were no commits or active maintainers in the last three months. Combined with the last registry release being in 2015, this is strong evidence that maintenance has stopped.

Repo toolingcaution

Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap, not a standalone severe risk.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package's long inactivity makes this gap more relevant.

Version stabilitycaution

The release is a non-stable 0.x version, which limits maturity confidence, although it is not marked as a prerelease.