arachne/service-collections

Release historydanger

Only three releases exist, with none in the last 12 months; the latest registry release was in December 2017. This long gap materially raises abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the prolonged release gap. The repository is not archived, but that does not offset the lack of current activity.

Repo popularitycaution

The repository has one star, four forks, and two watchers, indicating limited community visibility. Popularity is supporting evidence rather than a verdict, but it offers little compensating maintenance signal here.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, particularly for a dependency with no recent development activity.

Workflow auditcaution

No GitHub Actions workflows were present to audit, so there are no workflow findings, but this also provides no evidence of current automated maintenance or security checks.