opencontent/ocextensionsorder-ls

Release historydanger

The package has only two releases, with none in the last 12 months; its latest release was over eight years ago. This is strong evidence of abandonment risk despite the stable version.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The unarchived status does not show current maintenance.

Repo issue activitycaution

There has been no issue or pull request activity in the last month, offering no evidence of ongoing upkeep. With the stale release and commit history, this reinforces the maintenance concern.

Repo package mentioncaution

The repository name does not exactly match the package name, and no README mention was available to confirm the relationship. This creates some uncertainty about package provenance, although the organization ownership is a compensating signal.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security-scanning tooling was detected. This is a secondary transparency and maintenance gap rather than a standalone adoption blocker.