orchestra/translation

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the long release gap. This is the strongest evidence that the package is currently unmaintained.

Release historycaution

The package has 21 releases since 2013, but its latest release was about six years ago and it had no releases in the last 12 months. This long publishing gap materially raises maintenance and compatibility risk.

Repo toolingcaution

The repository uses Composer build tooling, but no security-scanning tools were detected. The missing scanning is a modest transparency gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy, reducing clarity about how vulnerabilities would be reported and handled. This matters more given the absence of recent maintenance activity.

Token permissionscaution

Both analyzed workflows omit top-level token permissions, so their effective permissions are less explicit than recommended. No workflow was found with explicitly broad write permissions.