openl10n/cli

Release historydanger

The latest release was published in March 2016, and there were no releases in the last 12 months. This long release gap is strong evidence of abandonment risk, despite the package having four releases overall.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months, confirming that current maintenance activity has effectively stopped.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while one issue and two pull requests remain open. This supports the picture of an inactive project.

Repo toolingcaution

Composer and Box provide an identifiable build process, but no security-scanning tools are configured. The missing scanning is a hygiene weakness rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy. For a command-line tool that handles server credentials, this reduces transparency around vulnerability reporting and response.