in4s/utest

Release historydanger

The package has six releases but none in the last 12 months, and its latest registry release was over four years ago. This is strong evidence of an inactive release line.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with a repository that has been inactive for years. This materially increases abandonment risk.

Maintainerscaution

Only one registry maintainer is listed, leaving limited visible publishing capacity. The linked repository is user-owned rather than organization-backed, so there is no provided evidence of a broader maintainer base to offset this.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a standalone adoption blocker.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This adds a transparency gap for a dependency that may require future fixes.